OpenSearch/client
Martijn van Groningen 417d5f2009
Make data streams in APIs resolvable. (#55337)
Backport from: #54726

The INCLUDE_DATA_STREAMS indices option controls whether data streams can be resolved in an api for both concrete names and wildcard expressions. If data streams cannot be resolved then a 400 error is returned indicating that data streams cannot be used.

In this pr, the INCLUDE_DATA_STREAMS indices option is enabled in the following APIs: search, msearch, refresh, index (op_type create only) and bulk (index requests with op type create only). In a subsequent later change, we will determine which other APIs need to be able to resolve data streams and enable the INCLUDE_DATA_STREAMS indices option for these APIs.

Whether an api resolve all backing indices of a data stream or the latest index of a data stream (write index) depends on the IndexNameExpressionResolver.Context.isResolveToWriteIndex().
If isResolveToWriteIndex() returns true then data streams resolve to the latest index (for example: index api) and otherwise a data stream resolves to all backing indices of a data stream (for example: search api).

Relates to #53100
2020-04-17 08:33:37 +02:00
..
benchmark Rename MetaData to Metadata in all of the places (#54519) 2020-03-31 17:24:38 -04:00
client-benchmark-noop-api-plugin Remove Xlint exclusions from gradle files 2020-02-20 14:12:05 +00:00
rest Remove deprecated third-party methods from tests (#55255) (#55269) 2020-04-15 17:54:47 -04:00
rest-high-level Make data streams in APIs resolvable. (#55337) 2020-04-17 08:33:37 +02:00
sniffer Use task avoidance with forbidden apis (#55034) 2020-04-15 13:27:53 -07:00
test Use task avoidance with forbidden apis (#55034) 2020-04-15 13:27:53 -07:00
transport [7.x] Re-add origin url information to publish POM files (#55173) 2020-04-14 13:24:15 -07:00