Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elasticsearch SQL

elastic.co

Post reply on HN
Print view View original

31–40 of 63 posts

Re: Elasticsearch SQL

#31

Post by dataminded »

ignoramous wrote: post #24
bearjaws wrote: post #10

I 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…

> ...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. It isn't that SQL is the best way (that these solutions keep gravitating towards it), it is just that SQL is pretty much the industry standard at this point. And supporting it is a predictable and usual ploy to expand userbase further. More so for the fact that ClickHouse continues to th…

What query languages have you found that are better than SQL?

[edit] Typo.

Re: Elasticsearch SQL

#32

Post by jedberg »

TotoHorner wrote: post #11
synthc wrote: post #3

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?

Cassandra added CQL which is very similar to but not exactly SQL.

Re: Elasticsearch SQL

#33

Post by deeebug »

munk-a wrote: post #26
bearjaws wrote: post #10

I 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…

Nothing could quite match my disappointment when I realized that Splunk (a large scale logging storage and retrieval product) decided to create a Splunk Query Language and eschew SQL... except maybe when I realized that they had no equivalent of `val IN(1,2,3...)` instead requiring `val = 1 OR val = 2 OR val = 3 ...` I have taught several non-techy business analyst type people how to write SQL during my years of empl…

Unsure if it was added recently, but Splunk Query Language does have VAL IN (1,2,3) now -> https://docs.splunk.com/Documentation/Splunk/9.0.1/SearchRef...

Re: Elasticsearch SQL

#35

Post by jrochkind1 »

jefurii wrote: post #23

Why the f*** couldn't they just build Elasticsearch with a SQL query language from the start? I hate their JSON query syntax and now that this is out I feel like I wasted all the time I spent making my applications work with it.

I guess one question, then, is why the f** you couldn't just have used an rdmbs instead of ES from the start....

Re: Elasticsearch SQL

#36

Post by matthewaveryusa »

munk-a wrote: post #26
bearjaws wrote: post #10

I 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…

Nothing could quite match my disappointment when I realized that Splunk (a large scale logging storage and retrieval product) decided to create a Splunk Query Language and eschew SQL... except maybe when I realized that they had no equivalent of `val IN(1,2,3...)` instead requiring `val = 1 OR val = 2 OR val = 3 ...` I have taught several non-techy business analyst type people how to write SQL during my years of empl…

And when those more complex concepts do come up and are too difficult to teach (or you want to lower the barrier of entry), you can always create a view that reduces the complexity back down to a select from.

Re: Elasticsearch SQL

#37

Post by bitsondatadev »

Trino is a nice query engine solution if you want to not just run SQL on Elasticsearch but also want to be able to join data from Elasticsearch with data in other systems Trino supports. It also supports raw elasticsearch queries that are serialized back into Trino data types.

https://trino.io/docs/current/connector/elasticsearch.html

Re: Elasticsearch SQL

#39

Post by Philip-J-Fry »

deeebug wrote: post #33
munk-a wrote: post #26

Earlier quoted context omitted.

Nothing could quite match my disappointment when I realized that Splunk (a large scale logging storage and retrieval product) decided to create a Splunk Query Language and eschew SQL... except maybe when I realized that they had no equivalent of `val IN(1,2,3...)` instead requiring `val = 1 OR val = 2 OR val = 3 ...` I have taught several non-techy business analyst type people how to write SQL during my years of empl…

Unsure if it was added recently, but Splunk Query Language does have VAL IN (1,2,3) now -> https://docs.splunk.com/Documentation/Splunk/9.0.1/SearchRef...

Splunk 7 added that from what I can find. 5 years old at least.

Re: Elasticsearch SQL

#40

Post by munk-a »

Philip-J-Fry wrote: post #39
deeebug wrote: post #33

Earlier quoted context omitted.

Unsure if it was added recently, but Splunk Query Language does have VAL IN (1,2,3) now -> https://docs.splunk.com/Documentation/Splunk/9.0.1/SearchRef...

Splunk 7 added that from what I can find. 5 years old at least.

I've been using it for quite a while.
Post reply on HN