Skip to content

Mappings: dynamic mapping updates should use the same path as mapping updates from the API #9364

@jpountz

Description

@jpountz

Currently we have two different code paths for dynamic mapping updates and mapping updates that come from the API.

I think we should improve it by making document parsing generate mapping updates, and then apply these mapping updates just like we apply mapping updates that come from the API.

This would probably help with #8688

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions