Seems like all the NoSQL databases eventually implement SQL, maybe we should use EventuallySQL instead NoSQL
What other prominent NoSQL databases eventually implemented SQL for queries?
Elasticsearch SQL
11–20 of 63 posts
Re: Elasticsearch SQL
#12I look forward to a future where everything is SQL at this point. It seems we have spent a significant amount of effort avoiding it, but it time and time again is the best way to query your data. I recently started using Steampipe and it has made my life about 30x better not having to deal with the AWS or Slack API. Essentially a tool to let you query their APIs using SQL, behind the scenes it boots up a Postgres dat…
The biggest upshot of SQL is that it makes migrating from one system to the next a lot easier. I can write something against SQLite or PostgreSQL, and when it comes time to move to $something_else for a particular aspect for some reason I ... just can, without having to rewrite the lot.
Of course, not all is perfect because no one actually supports ANSI SQL, and everyone has their own extensions and incompatibilities so you'll probably have to at least tweak some things. Besides, string concatenation isn't exactly a fantastic way to communicate with a database in the first place. But at this point it's pretty much the only thing we've got that's even vaguely universal.
Re: Elasticsearch SQL
#13I’m conflicted on efforts like this. On the one hand SQL is for better or worse the Lingua Franca of database interfaces. On the other hand these half hearted, castrated implementations rarely work with tools geared towards working with true relational stores. The only real gain here is the surface level familiarity and of course the big fat check mark that the marketing team can put on the brochure to say “why, yes…
Having spent entirely too much of my life working with Elastic's annoyingly verbose and confusing JSON query syntax, the SQL is a big upgrade here even if it's not 1:1 with relational DBs.
Re: Elasticsearch SQL
#14As I recall, this is severely limited in that it does not correctly support sub-searches or pivoting between different indexes. Any news on if this has been improved?
Re: Elasticsearch SQL
#15Seems like all the NoSQL databases eventually implement SQL, maybe we should use EventuallySQL instead NoSQL
MongoDB took about 8 years to fully implement SQL features but they forced it into their god-awful syntax. At least Elastic stuck with SQL?
MongoDB has an SQL interface these days if you need it
Re: Elasticsearch SQL
#16Earlier quoted context omitted.
MongoDB took about 8 years to fully implement SQL features but they forced it into their god-awful syntax. At least Elastic stuck with SQL?
MongoDB has an SQL interface these days if you need it https://www.mongodb.com/atlas/sql
That is absolutely hilarious
Re: Elasticsearch SQL
#17Re: Elasticsearch SQL
#18Just as an FYI for folks, you could query Elasticsearch via SQL with Apache Calcite:
Re: Elasticsearch SQL
#19It's pretty cool for light work, but I imagine you would be better off doing native ES queries so when you need more complex queries, weighted searches, and optimizations, you will be in a better place to do that.
Re: Elasticsearch SQL
#20I look forward to a future where everything is SQL at this point. It seems we have spent a significant amount of effort avoiding it, but it time and time again is the best way to query your data. I recently started using Steampipe and it has made my life about 30x better not having to deal with the AWS or Slack API. Essentially a tool to let you query their APIs using SQL, behind the scenes it boots up a Postgres dat…
The syntax is still backward though.
> SELECT blah FROM source
vs
> FROM source SELECT blah
Fixing this would permit some very useful developer features.