com.sksamuel.elastic4s.testkit
(Since version 5.0.0) Use xxxAggregation(...) methods
(Since version 5.0.0) this usage leads to subtle bugs, please use boolQuery().must(...).should(...).not(...)
(Since version 5.0.0) use commonQuery(field
(Since version 6.0.0) Use deleteById(index, id) which only supports deleting by index, not by index and type. This is because in version 6 of Elasticsearch types are deprecated https://www.elastic.co/guide/en/elasticsearch/reference/master/removal-of-types.html.
(Since version 6.0.0) Use deleteByQuery(index, query) which only supports deleting by index, not by index and type. This is because in version 6 of Elasticsearch types are deprecated https://www.elastic.co/guide/en/elasticsearch/reference/master/removal-of-types.html.
(Since version 5.2.12) use dynamicIntField(), dynamicTextField() and so on
(Since version 5.0.0) use field(name, type)
(Since version 5.2.11) use tokenCountField(name)
(Since version 5.2.11) use textField(name)
(Since version 5.2.11) use shortField(name)
(Since version 5.2.11) use percolatorField(name)
(Since version 5.2.11) use objectField(name)
(Since version 5.2.11) use nestedField(name)
(Since version 5.2.11) use longField(name)
(Since version 5.2.11) use keywordField(name)
(Since version 5.2.11) use ipField(name)
(Since version 5.2.11) use intField(name)
(Since version 5.2.11) use geoshapeField(name)
(Since version 5.2.11) use geopointField(name)
(Since version 5.2.11) use floatField(name)
(Since version 5.2.11) use doubleField(name)
(Since version 5.2.11) use dateField(name)
(Since version 5.2.11) use completionField(name)
(Since version 5.2.11) use byteField(name)
(Since version 5.2.11) use booleanField(name)
(Since version 5.2.11) use binaryField(name)
(Since version 5.3.3) Use bool query directly
(Since version 5.3.3) Use bool query directly
(Since version 5.2.0) use geoPolygonQuery
(Since version 6.0.0) Use the stored scripts api to get templates
(Since version 6.0) Elasticsearch 6.0 has deprecated types with the intention of removing them in 7.0. You can continue to use them in existing indexes, but all new indexes must only have a single type. Use the index(indexName) method instead which will default to using a type with the same name as the index.
(Since version 6.0) Elasticsearch 6.0 has deprecated types with the intention of removing them in 7.0. You can continue to use them in existing indexes, but all new indexes must only have a single type. Use the index(indexName) method instead which will default to using a type with the same name as the index.
(Since version 6.0) Elasticsearch 6.0 has deprecated types with the intention of removing them in 7.0. You can continue to use them in existing indexes, but all new indexes must only have a single type. Use the index(indexName) method instead which will default to using a type with the same name as the index.
(Since version 5.2.0) use matchQuery(field, value) instead of the tupled version
(Since version 6.0.0) Use the stored scripts api to store templates
(Since version 6.0.0) Use the stored scripts api to store templates
(Since version 5.0.0) use refreshIndex(index)
(Since version 6.0.0) Use the stored scripts api to delete templates
(Since version 6.0) Elasticsearch 6.0 has deprecated types with the intention of removing them in 7.0. You can continue to use them in existing indexes, but all new indexes must only have a single type. Therefore searching across multiple types is now deprecated because types will no longer work in the next release.
(Since version 6.0) Elasticsearch 6.0 has deprecated types with the intention of removing them in 7.0. You can continue to use them in existing indexes, but all new indexes must only have a single type. Therefore searching across multiple types is now deprecated because types will no longer work in the next release.
(Since version 5.0.0) string type is deprecated in ES 5, use text or keyword types
use index / type not index -> type