You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To handle type mappings deprecation, a customer may split a single source index into multiple target indexes.
Say a user has a source index twitter with multiple types tweet and user, the user configures the TypeMappingsSanitizationTransformerProvider to map tweet docs to twitter_tweet and user docs to twitter_user.
When a request is captured as an operation on the index twitter, e.g. update refresh interval, the replayer would be expected to apply this operation on both twitter_tweet and twitter_user target indexes.
This is not currently supported.
What are your migration environments?
Applies to source ES <= 6 (indexes created on ES <= 5)
What is the expected behavior?
The replayer supports 1:many request transformations and TypeMappingsSanitizationTransformerProvider natively handles index operations with split behavior.