New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more examples needed for druid sql #6108
Comments
Hi @pdeva, the answers to your questions are,
I agree an examples section would be nice; @jon-wei was working on some new tutorials for querying, maybe he can chime in with whether he had planned on adding SQL examples. |
I have one example query for "wikipedia top pages" in the new tutorials (the idea was more to show the tools/workflow vs being a tutorial on expressing queries in SQL, do you have any suggestions for common queries that would be good examples? |
@gianm clarifying:
|
(3) sounds like it's really the same question as (2), and TIME_FLOOR is the answer. (4) adheres to standard SQL: result rows are only emitted where there is actual data. So there would be no row for 10am–11am. |
Maybe four queries: one that plans to a scan, one that plans to a timeseries, one that plans to a topN, and one that plans to a groupBy? And link to that from the SQL docs so people know where to go to find examples? |
@gianm regarding 4. is the behavior of native queries (topn, timeseries, groupby) the same as sql for this case? in that will they omit 10-11 from the results too? |
topN and groupBy will; for timeseries it depends on the skipEmptyBuckets setting. |
The new query tutorial has more SQL examples: http://druid.io/docs/latest/tutorials/tutorial-query.html (0.12.2/0.12.3)
Virtual columns are now documented: http://druid.io/docs/latest/querying/virtual-columns.html |
druid __time how to transfer datetime |
druid sql is very highly under documented to the point of being unsuable.
at the very least, there should be example queries showing:
Interval(begin, end)
or is a fullbegin>= x and end <=y
needed every timeThe text was updated successfully, but these errors were encountered: