nice post :)

Classic

All good, I think we're still a step before doing that

no clue

I just try not to run too many apps at the same time now :(

So annoying. Need the next update to fix this haha

What is your take on Elasticsearch shipping a SQL interface?

I'm not as familiar with this use case, but I don't see how this couldn't be declared as SQL.

We came up with this categorization internally:

- real-time search (e.g. dashboards, SaaS search boxes)
- observability
- RAG/GenAI

Instacart can know this because they have recommender systems trained on what this user might want.

But I don't think all search use cases need this. I suspect AI-search use cases will to a lesser extent, but that it'll be beneficial for them. That's more likely to be an area we optimize around.

By arbitrary, you mean custom code / ML models? I think these matter a lot in a use case like e-commerce where a lot of domain knowledge and user-specific knowledge is applied. For example, an Instacart user might type "banana" but they want "banana yogurt" rather than "bananas".