FORCE_NEW is not used in Elasticsearch-py

stable/0.4.x
Karl Hobley 2014-07-14 10:58:50 +01:00 zatwierdzone przez Matt Westcott
rodzic 930833324d
commit cc446f0e97
1 zmienionych plików z 1 dodań i 2 usunięć
docs/search

Wyświetl plik

@ -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: