-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding TransportSimulateShardBulkAction #108795
Adding TransportSimulateShardBulkAction #108795
Conversation
Pinging @elastic/es-data-management (Team:Data Management) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay here, this is on my radar to get to but have not found the time yet.
Closing in favor of #109889, which avoids simulate using a ShardBulkAction (and still allows for the possibility of mapping validation in the future). |
This adds a TransportSimulateShardBulkAction, meant to be used in simulate ingest in place of TransportShardBulkAction. This delegates virtually all of its logic to TransportShardBulkAction. However, TransportShardBulkAction is a WriteAction and TransportSimulateShardBulkAction is not -- TransportSimulateShardBulkAction does not change state in any way (cluster state, shards, or translog). Since it does not write to shards, it does not need to perform a refresh.
This PR does not actually wire TransportSimulateShardBulkAction up for use by the simulate ingest API (or anything else). See #106440 for the full draft where it is called by BulkOperation (which is called due to the changes in TransportSimulateBulkAction in that PR).
Relates to #108791