From cc446f0e9735d0f051e5608e22203f498a2412c2 Mon Sep 17 00:00:00 2001 From: Karl Hobley Date: Mon, 14 Jul 2014 10:58:50 +0100 Subject: [PATCH] FORCE_NEW is not used in Elasticsearch-py --- docs/search/backends.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/search/backends.rst b/docs/search/backends.rst index f03f06358..471da751a 100644 --- a/docs/search/backends.rst +++ b/docs/search/backends.rst @@ -41,11 +41,10 @@ The backend is configured in settings: 'URLS': ['http://localhost:9200'], 'INDEX': 'wagtail', 'TIMEOUT': 5, - 'FORCE_NEW': False, } } -Other than ``BACKEND`` the keys are optional and default to the values shown. ``FORCE_NEW`` is used by elasticsearch-py. In addition, any other keys are passed directly to the Elasticsearch constructor as case-sensitive keyword arguments (e.g. ``'max_retries': 1``). +Other than ``BACKEND`` the keys are optional and default to the values shown. In addition, any other keys are passed directly to the Elasticsearch constructor as case-sensitive keyword arguments (e.g. ``'max_retries': 1``). If you prefer not to run an Elasticsearch server in development or production, there are many hosted services available, including `Searchly`_, who offer a free account suitable for testing and development. To use Searchly: