"Schema on reads" is a mechanism where query result data can be defined at runtime of the query. This is useful for users who may not be aware of the structure of the data and want to explore its usage before choosing what and how to index it. More simply, this allows users to have additional attributes to query upon post-ingest. Derived fields are an enhancement to OpenSearch that provides this "schema on read" functionality.
[Triage - attendees 12345678]
@qreshi Thanks for filing, it would be useful to to create subtasks with additional details for some of those items, looking forward to seeing progress here.
[ ] Allow removal of derived fields from index mappings
[ ] Support with concurrent segment search. LeafLookup instance shared among segments within a slice could be problem, assess if its a problem and how to fix it.
Please describe the end goal of this project
"Schema on reads" is a mechanism where query result data can be defined at runtime of the query. This is useful for users who may not be aware of the structure of the data and want to explore its usage before choosing what and how to index it. More simply, this allows users to have additional attributes to query upon post-ingest. Derived fields are an enhancement to OpenSearch that provides this "schema on read" functionality.
Supporting References
The RFC for this feature request can be found here https://github.com/opensearch-project/OpenSearch/issues/1133
Issues
I will update this section with created issues with more details. For the time being I wanted to create the META issue for tracking.