Stavros Macrakis

@andreaAlkalay Can you tell us more about your business scenario and why the flattened type is important to it? Thanks.

# [Design Proposal] The *flat* data type in OpenSearch ## Summary JSON objects whose components are not indexed are a proposed new field type in OpenSearch; we call them **flat**...

@mrkamel @abhishek-v @reta @andreaAlkalay @amalgamm @lukas-vicek The current Design Proposal is intentionally minimal. It covers the core functionality of the flat data type, namely ingesting nested objects as a single...

Thanks for the presentation today. I would like to understand how a sys admin would use sandboxes for the following scenarios: Classic search on the web, e.g., e-commerce (see the...

Credit for most of the software for the Gould printer, the Grinnell frame buffers, etc. goes to John Kulp and Charles Karney, if I'm not mistaken. I've CC'd them so...

@epiphone Could you describe your use case? I do understand that it speeds up wildcard searches, but why is wildcard search performance critical in your application? How many unique values...

Josef, Epiphone, thanks for your answers -- very helpful! So it sounds like you need to find *arbitrary* substrings in your corpus, not just strings starting at token boundaries. That...

Re using wildcard field for XML (https://github.com/opensearch-project/OpenSearch/issues/5639#issuecomment-1422345013), I wonder if you could use the XML logstash filter and then the Flat field type which is coming out in 2.7? (https://github.com/opensearch-project/OpenSearch/issues/1018#issuecomment-1188365805).