Wykres commitów

9 Commity (fb0742802f2d738ae3de8b589139a5a93559bcc5)

Autor SHA1 Wiadomość Data
pySilver 0149eff66a Implements ES7 support (#5611)
* Implements ES7 support

* Linter fix

* Adds docs

* isort fix

* Fixes typo
2019-10-10 11:00:14 +01:00
Karl Hobley cac3a65a3d Travis/tox configuration for Elasticsearch 6 2018-05-04 15:57:36 +01:00
Karl Hobley 0a52196c63 Remove ES 1.x from test configuration 2017-11-06 14:27:27 +00:00
Matt Westcott 16439193a3 Update Travis config to work with on Trusty architecture (#3739)
* Update Travis config to work with on Trusty architecture

* Explicitly specify Trusty environment
2017-07-28 18:48:01 +01:00
Matt Westcott ad3e4c3d53 Install Elasticsearch 5.3.3 for Travis
5.4 has a bug in testing existence of aliases which causes tests to fail: https://github.com/elastic/elasticsearch/issues/24644
2017-06-07 15:08:48 +01:00
Karl Hobley 6be679e19f Set vm.max_map_count to 262144 2016-11-30 16:31:20 +00:00
Karl Hobley 35c850d8ec Update URLs in install_elasticsearch5.sh 2016-11-30 16:31:20 +00:00
Karl Hobley 752fbca24a Add Elasticsearch 5 to Travis/tox 2016-11-30 16:31:20 +00:00
Karl Hobley daa82936d7 Elasticsearch 2 support (#2573)
* Created Elasticsearch 2 backend

* Added tests for Elasticsearch 2 backend

* Split models up into different indices

pages, images and documents are now in separate indices

* Prefix fields of child models to prevent mapping clashes

* Replaced index_analyzer with analyzer/search_analyzer

index_analyzer has been removed in Elasticsearch 2.0

https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_analyzer_mappings

There's no indication in Elasticsearch's docs that this wouldn't work on Elasticsearch 1.x. However, we found that the new configuration isn't reliable on Elasticsearch 1.6 and below (causes the test_query_analyzer test to fail randomly).

* Implemented new way of representing content types in search index

Instead of using a long string of model names that is queried using a
"prefix" query, we instead use a multi-value string field and query it
using a simple "match" query.

The only reason why this isn't implemented in the Elasticsearch 1.x
backend yet is backwards compatibility

* Added another child model of SearchTest with clashing field mapping

This checks that the namespacing of fields on child models is working properly (if it doesn't the update_index tests will fail)

* Added tests for get_model_root function

* fixup! Added tests for get_model_root function

* Docs updates for Elasticsearch 2 support

Also tweak examples to use elasticsearch2 backend by default

* Test against Elasticsearch 2 on travis
2016-08-31 13:46:57 +03:00