honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/reference/migration/migrate_6_0/java.asciidoc

29 lines
1.6 KiB
Plaintext
Raw Normal View History

Enforce Content-Type requirement on the rest layer and remove deprecated methods (#23146) This commit enforces the requirement of Content-Type for the REST layer and removes the deprecated methods in transport requests and their usages. While doing this, it turns out that there are many places where *Entity classes are used from the apache http client libraries and many of these usages did not specify the content type. The methods that do not specify a content type explicitly have been added to forbidden apis to prevent more of these from entering our code base. Relates #19388
2017-02-17 14:45:41 -05:00
[[breaking_60_java_changes]]
=== Java API changes
==== `setSource` methods require XContentType
Previously the `setSource` methods and other methods that accepted byte/string representations of
an object source did not require the XContentType to be specified. The auto-detection of the content
type is no longer used, so these methods now require the XContentType as an additional argument when
providing the source in bytes or as a string.
Require explicit query in _delete_by_query API (#23632) As the query of a search request defaults to match_all, calling _delete_by_query without an explicit query may result in deleting all data. In order to protect users against falling into that pitfall, this commit adds a check to require the explicit setting of a query. Closes #23629
2017-03-28 10:44:57 -04:00
Java api: ActionRequestBuilder#execute to return a PlainActionFuture (#24415) This change makes the request builder code-path same as `Client#execute`. The request builder used to return a `ListenableActionFuture` when calling execute, which allows to associate listeners with the returned future. For async execution though it is recommended to use the `execute` method that accepts an `ActionListener`, like users would do when using `Client#execute`. Relates to #24412 Relates to #9201
2017-05-03 05:20:53 -04:00
==== `DeleteByQueryRequest` requires an explicitly set query
Require explicit query in _delete_by_query API (#23632) As the query of a search request defaults to match_all, calling _delete_by_query without an explicit query may result in deleting all data. In order to protect users against falling into that pitfall, this commit adds a check to require the explicit setting of a query. Closes #23629
2017-03-28 10:44:57 -04:00
In previous versions of Elasticsearch, delete by query requests without an explicit query
were accepted, match_all was used as the default query and all documents were deleted
as a result. From version 6.0.0, a `DeleteByQueryRequest` requires an explicit query be set.
Remove getCountAsString() from InternalStats and Stats interface (#24291) The `count` value in the stats aggregation represents a simple doc count that doesn't require a formatted version. We didn't render an "as_string" version for count in the rest response, so the method should also be removed in favour of just using String.valueOf(getCount()) if a string version of the count is needed. Closes #24287
2017-04-24 12:40:57 -04:00
Java api: ActionRequestBuilder#execute to return a PlainActionFuture (#24415) This change makes the request builder code-path same as `Client#execute`. The request builder used to return a `ListenableActionFuture` when calling execute, which allows to associate listeners with the returned future. For async execution though it is recommended to use the `execute` method that accepts an `ActionListener`, like users would do when using `Client#execute`. Relates to #24412 Relates to #9201
2017-05-03 05:20:53 -04:00
==== `InternalStats` and `Stats` getCountAsString() method removed
Remove getCountAsString() from InternalStats and Stats interface (#24291) The `count` value in the stats aggregation represents a simple doc count that doesn't require a formatted version. We didn't render an "as_string" version for count in the rest response, so the method should also be removed in favour of just using String.valueOf(getCount()) if a string version of the count is needed. Closes #24287
2017-04-24 12:40:57 -04:00
The `count` value in the stats aggregation represents a doc count that shouldnn't require a formatted
version. This method was deprecated in 5.4 in favour of just using
`String.valueOf(getCount())` if needed
Java api: ActionRequestBuilder#execute to return a PlainActionFuture (#24415) This change makes the request builder code-path same as `Client#execute`. The request builder used to return a `ListenableActionFuture` when calling execute, which allows to associate listeners with the returned future. For async execution though it is recommended to use the `execute` method that accepts an `ActionListener`, like users would do when using `Client#execute`. Relates to #24412 Relates to #9201
2017-05-03 05:20:53 -04:00
==== `ActionRequestBuilder#execute` returns `ActionFuture` rather than `ListenableActionFuture`
When sending a request through the request builders e.g. client.prepareSearch().execute(), it used to
be possible to call `addListener` against the returned `ListenableActionFuture`. With this change an
`ActionFuture` is returned instead, which is consistent with what the `Client` methods return, hence
it is not possible to associate the future with listeners. The `execute` method that accept a listener
as an argument can be used instead.