Michael Froh

I actually found what I believe is a pretty safe fix for the underlying issue that should have no effect on any "normal" index, where the fields being searched are...

> Example: a textEmbedding processor can convert 1 or more fields of a document to embedding but in a SearchRequestProcessor works on a field of the queryRequest. The common document...

I tried doing some Googling, but couldn't find anything that documents the existence of `_recovery_source` or explains what it does, other than the source code. I think we would need...

Still failing for me: https://build.ci.opensearch.org/job/gradle-check/38635/testReport/junit/org.opensearch.indices/IndicesRequestCacheIT/testDeleteAndCreateSameIndexShardOnSameNode__p0___search_concurrent_segment_search_enabled___false___/

Aha! While implementing search pipelines (and copying from ingest pipelines), I considered adding `final_pipeline` support. One question that I left unanswered was whether the flow should be: ```mermaid flowchart LR...

> No its not feasible to add assertion of segment count - I could not find a utility to do so in our codebase. Introducing such utility may not be...

> @msfroh @harshavamsi what do you think about order in which we should scan the segments here? If we start with the smaller segments and if the field is found,...

Does this belong in https://github.com/opensearch-project/flow-framework ? It doesn't seem to be related to OpenSearch core.

I would just like to point out that no (ingest or search) processors in OpenSearch operate on JSON. They operate on (Java) objects. JSON is just a *notation* to represent...

There was some good discussion over on https://github.com/opensearch-project/OpenSearch/issues/12500, which highlighted the value of wildcard fields. Also, Elastic's blog post about the feature provides a really good explanation: https://www.elastic.co/blog/find-strings-within-strings-faster-with-the-new-elasticsearch-wildcard-field