Repository navigation
[Slice] Introduce initial _slice API changes - #147185
Conversation
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
jimczi
left a comment
There was a problem hiding this comment.
Looks good! I left one comment regarding the new parameter on index request.
I also wonder how delete works? Do we need the same change to handle deletes with slice similarly to how update works?
| private String id; | ||
| @Nullable | ||
| private String routing; | ||
| private boolean routingFromSlice; |
There was a problem hiding this comment.
This value is not written on serialization so currently it is lost when transport is used?
There was a problem hiding this comment.
@jimczi yes, I am testing a bunch of edge cases to see if we actually need a transport layer change for this.
I am suspecting, yes, when I move to add delete and update. But didn't exactly see the need for it here.
Future PR! And |
This is the first of likely many PRs.
Introduces:
_sliceon PUT/POST/BULK/UPDATE