[i_am_a_squirrel]

> Say goodbye to the complexity of crafting queries by code.

IDK about this angle, just because elasticsearch / SQL has fucky syntax doesn't mean that crafting queries in code is something we wanna say goodbye to?

I like what Google Malloy has done, it made writing things in code enjoyable by reinventing the syntax and language, but keeping it compatible with existing tech.

Otherwise this is cool! I found it daunting as a newcomer to search thinking about optimizing search and making sense of how users use it.

But even with elasticsearch, it was not that hard to craft queries to do a faceted search and it was cheap and easy to setup, so the value I see is more in the analysis. And if you're going beyond a faceted search with basic group and / or logic, then isn't vector searches the way to go anyway?

I'm probably missing something!

[giulioco]

Good point. While the visual query builder is meant to be more like a playground to play around while crafting your queries, at the end of the day it just provides you with an API request body (json) that can also be hand-crafted. The VQB is also a way to craft and save query “aliases” with their own permissions.

Analytics: our painpoint with a few other search solutions was a lack of out-of-the-box insights for user behavior and common searches. We’re addressing this with Searchbase

[ofiryanai]

Vector search is no replacement for complex logic, its merely another data type like bm25 ir regular range filter. Searchbase looks to me as better fit for intuitive data exploration, rather than replacing existing robust high throughput searches