ElasticDsl
Related Docs:
trait ElasticDsl
| package http
(Since version 6.1.2) use geoDistanceQuery(field, hash) or geoDistanceQuery(field, lat, long)
(Since version 5.0.0) this usage leads to subtle bugs, please use boolQuery().must(...).should(...).not(...)
(Since version 6.1.2) use commonTermsQuery
(Since version 6.1.2) use commonTermsQuery
(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.
(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.
(Since version 6.0.2) use createRepository(name: String, repository: String)
(Since version 6.0.2) use createSnapshot(name: String, repository: String)
(Since version 6.0.0) use createIndexTemplate(name: String, pattern: String)
(Since version 6.0.0) use createIndexTemplate(name: String, pattern: String)
(Since version 6.0.2) use deleteSnapshot(name: String, repository: String)
(Since version 6.0.0) use deleteIndexTemplate(name)
(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 6.1.2) use existsQuery with _field_names
(Since version 6.1.2) use existsQuery with _field_names
(Since version 5.3.3) Use bool query directly
(Since version 5.3.3) Use bool query directly
(Since version 6.0.0) use getAliases(indexes, aliases), where you can pass in Nil for indexes or aliases to act as a wildcard
(Since version 6.0.0) use getAliases(indexes, aliases), where you can pass in Nil for indexes or aliases to act as a wildcard
(Since version 6.0.0) Use the stored scripts api to get templates
(Since version 6.0.2) use getSnapshot(name: String, repository: String)
(Since version 6.0.2) use getSnapshot(name: String, repository: String)
(Since version 6.0.0) use getIndexTemplate(name)
(Since version 5.2.0) use matchQuery(field, value) instead of the tupled version
(Since version 6.1.2) use the non-tupled version prefixQuery(field,value)
(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 6.1.2) use the non-tupled version regexQuery(field,value)
(Since version 6.0.0) use reindex(from, to)
(Since version 6.0.0) Use the stored scripts api to delete templates
(Since version 6.0.2) use restoreSnapshot(name: String, repository: String)
(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 it will be removed in the next major release and you are encourged to move your code to use search without types. To remove this warning use the 6.0 method searchWithType()
(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 it will be removed in the next major release and you are encourged to move your code to use search without types. To remove this warning use the 6.0 method searchWithType()
(Since version 6.1.2) use shrinkIndex(source, target)
(Since version 6.1.2) use the non-tupled version termQuery(field,value)
use index / type not index -> type
(Since version 6.1.2) use the non-tupled version wildcardQuery(field,value)