Deprecated API
Contents
-
ClassDescriptionSince max_optimization optimization landed in 7.0, normal MatchQuery will achieve the same result without any configuration.
TransportClient
is deprecated in favour of the High Level REST client and will be removed in Elasticsearch 8.0.Since max_optimization optimization landed in 7.0, normal MatchQuery will achieve the same result without any configuration.
-
ExceptionsDescriptionUse ScriptException for exceptions from the scripting engine, otherwise use a more appropriate exception (e.g. if thrown from various abstractions)This exception isn't thrown anymore. It's only here for BwC.
-
Annotation InterfaceDescription
FactoryProvider
now works better with the standard @Inject annotation. When using that annotation, parameters are matched by name and type rather than by position. In addition, values that use the standard @Inject constructor annotation are eligible for method interception.
-
FieldDescriptiondeclare your own logger.transition mechanism only, do not useSince max_optimization optimization landed in 7.0, normal MatchQuery will achieve the same result without any configuration.please use MAX_DOCS_ALL_MATCHES instead.declare your own logger.
-
MethodDescriptionSince max_score optimization landed in 7.0, normal MultiMatchQuery will achieve the same result without any configuration.Transient settings are in the process of being removed. Use persistent settings to update your cluster settings instead.Transient settings are in the process of being removed. Use persistent settings to update your cluster settings instead.Transient settings are in the process of being removed. Use persistent settings to update your cluster settings instead.Transient settings are in the process of being removed. Use persistent settings to update your cluster settings instead.Transient settings are in the process of being removed. Use persistent settings to update your cluster settings instead.Types are in the process of being removed. Instead of using a type, prefer to filter on a field on the document.Types are in the process of being removed. Instead of using a type, prefer to filter on a field on the document.Use
BulkProcessor.builder(BiConsumer, Listener, String)
with client::bulk as the first argument, orBulkProcessor.builder(org.elasticsearch.client.Client, org.elasticsearch.action.bulk.BulkProcessor.Listener, org.elasticsearch.threadpool.Scheduler, org.elasticsearch.threadpool.Scheduler, java.lang.Runnable)
and manage the flush and retry schedulers explicitlyorg.elasticsearch.action.bulk.BulkRequest.add(BytesReference, String, String, boolean, XContentType) org.elasticsearch.action.bulk.BulkRequestBuilder.add(byte[], int, int, String, String, XContentType) Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.UseGetResponse.getSource()
insteadTypes are in the process of being removed, useMultiGetRequest.add(String, String)
instead.Types are in the process of being removed.Types are in the process of being removed.Types are in the process of being removed.This option is only available temporarily. Instead of using this setter directly, use the parameter on the rest request. The bwc emulation will not be necessary on 8.0 any more, so this setter will not be availabe there.Types are in the process of being removed. Instead of using a type, prefer to filter on a field on the document.Types are in the process of being removed. Instead of using a type, prefer to filter on a field on the document.Types are going away, prefer filtering on a field.Types are in the process of being removed.useTermVectorsRequest.doc(BytesReference, boolean, XContentType)
to avoid content auto detectionUseUpdateRequest.script(Script)
insteadTypes are in the process of being removed.UseUpdateRequest.script(Script)
insteadUseUpdateRequest.script(Script)
insteadUseUpdateRequest.script(Script)
insteadUseUpdateRequest.script(Script)
insteadUseUpdateRequest.script()
insteadUseUpdateRequest.script(Script)
insteadUseUpdateRequest.script()
insteadUseUpdateRequest.script(Script)
insteadUseUpdateRequest.script()
insteadUseUpdateRequest.script()
insteadTypes are in the process of being removed.Types are in the process of being removed.Types are deprecated and are in the process of being removed.Types are deprecated and are in the process of being removed.Types are deprecated and are in the process of being removed.UseIndexMetadata.mapping()
instead now that indices have a single typeremove this when multihoming is really correctWe're in the process of abstracting offset *into* Rounding so keep any usage to migratory shimsPreferRounding.prepare(long, long)
and thenRounding.Prepared.round(long)
this method relies on auto-detection of content type. UseXContentHelper.convertToMap(BytesReference, boolean, XContentType)
instead with the properXContentType
useXContentHelper.createParser(NamedXContentRegistry, DeprecationHandler, BytesReference, XContentType)
to avoid content type auto-detectionuseXContentHelper.writeRawField(String, BytesReference, XContentType, XContentBuilder, Params)
to avoid content type auto-detectionthe content type should not be guessed except for few cases where we effectively don't know the content type. The REST layer should move to reading the Content-Type header instead. There are other places where auto-detection may be needed. This method is deprecated to prevent usages of it from spreading further without specific reasons.Don't swallow exceptions, allow them to propagate.This setting will be removed in 8.0we are actively deprecating and removing the ability to pass complex objects to multifields, so try and avoid using this methodTypes are in the process of being removed.Types are in the process of being removed, prefer to filter on a field instead.Types are in the process of being removed, prefer to filter on a field instead.seeMatchQueryBuilder.CUTOFF_FREQUENCY_FIELD
for more detailsTypes are in the process of being removed.Types are in the process of being removed.Since max_score optimization landed in 7.0, normal MultiMatchQuery will achieve the same result without any configuration.Since max_score optimization landed in 7.0, normal MultiMatchQuery will achieve the same result without any configuration.Types are in the process of being removed, useQueryBuilders.geoDisjointQuery(String, String)
instead.Types are in the process of being removed, useQueryBuilders.geoIntersectionQuery(String, String)
instead.Types are in the process of being removed, useQueryBuilders.geoShapeQuery(String, String)
instead.Types are in the process of being removed, useQueryBuilders.geoWithinQuery(String, String)
instead.Types are in the process of being removed, useQueryBuilders.idsQuery()
instead.Types are going away, prefer filtering on a field.please use getMaxDocs() instead.please use setMaxDocs(int) instead.please use maxDocs(int) instead.Types are in the process of being removed. Instead of using a type, prefer to filter on a field of the document.Types are in the process of being removed. Instead of using a type, prefer to filter on a field of the document.Types are in the process of being removed. Instead of using a type, prefer to filter on a field of the document.Types are in the process of being removed. Instead of using a type, prefer to filter on a field of the document.Specifying a sort field for reindex is deprecated. If using this in combination with maxDocs, consider using a query filter instead.Types are in the process of being removed. Instead of using a type, prefer to filter on a field of the document.Types are in the process of being removed. Instead of using a type, prefer to filter on a field of the document.SeeMatchQueryParser.setCommonTermsCutoff(Float)
for more detailsIndex types are going away over the next two major releases. New system indices should accept the default, which isMapperService.SINGLE_MAPPING_NAME
.Types are in the process of being removed.Pipelines implemented after 7.8.0 do not need to be sent across the wirethis method is only used when taking snapshots in a mixed version cluster where a master node older thanSnapshotsService.NO_REPO_INITIALIZE_VERSION
is present.only use these for serializing to older Elasticsearch versionsthese only exist for BWC serializationpipeline aggregations added after 7.8.0 don't need to implement thispipeline aggregations added after 7.8.0 don't need to implement thispipeline aggregations added after 7.8.0 shouldn't call thisTypes are in the process of being removed. Instead of using a type, prefer to filter on a field on the document.set nested sort withFieldSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withFieldSortBuilder.getNestedSort()
set nested sort withFieldSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withFieldSortBuilder.getNestedSort()
set nested sort withFieldSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withFieldSortBuilder.getNestedSort()
set nested sort withFieldSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withFieldSortBuilder.getNestedSort()
set nested sort withGeoDistanceSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withGeoDistanceSortBuilder.getNestedSort()
set nested sort withGeoDistanceSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withGeoDistanceSortBuilder.getNestedSort()
set nested sort withGeoDistanceSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withGeoDistanceSortBuilder.getNestedSort()
set nested sort withGeoDistanceSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withGeoDistanceSortBuilder.getNestedSort()
set nested sort withScriptSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withScriptSortBuilder.getNestedSort()
set nested sort withScriptSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withScriptSortBuilder.getNestedSort()
set nested sort withScriptSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withScriptSortBuilder.getNestedSort()
set nested sort withScriptSortBuilder.setNestedSort(NestedSortBuilder)
and retrieve withScriptSortBuilder.getNestedSort()
-
ConstructorDescriptionTypes are in the process of being removed. Use
BulkRequest(String)
insteadTypes are in the process of being removed. UseDeleteRequest(String, String)
instead.Types are in the process of being removed. Useinstead.
Types are in the process of being removed, useGetRequest(java.lang.String,java.lang.String)
instead.Types are in the process of being removed, useinstead
.Types are in the process of being removed. UseIndexRequest(String)
instead.Types are in the process of being removed. UseIndexRequest(String)
withIndexRequest.id(String)
instead.Types are in the process of being removed. UseUpdateRequest(String, String)
instead.Only use for compatibility between deprecated string settings and new secure stringsuseAbstractGeometryQueryBuilder(String, String)
insteadSeeCommonTermsQueryBuilder
for more details.SeeCommonTermsQueryBuilder
for more details.useGeoShapeQueryBuilder(String, String)
insteadTypes are in the process of being removed, useItem(java.lang.String,java.lang.String)
instead.Types are in the process of being removed, useItem(java.lang.String,org.elasticsearch.xcontent.XContentBuilder)
instead.Types are in the process of being removed, useTermsLookup(java.lang.String,java.lang.String,java.lang.String)
instead.Use the ctor that takes aContextParser
insteadUse the ctor that takes aContextParser
insteadprefer the ctor that takes aContextParser
UsePipelineAggregationSpec(String, Writeable.Reader, ContextParser)
for pipelines implemented after 7.8.0prefer the ctor that takes aContextParser
UsePipelineAggregationSpec(ParseField, Writeable.Reader, ContextParser)
for pipelines implemented after 7.8.0pipeline aggregations added after 7.8.0 shouldn't call this