-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
SQL: Add context and contextual functions to planner. #3919
Conversation
This probably could be broken up into two smaller PRs (1- context, 2- time related stuff), but I did it as one since I ended up developing a few related things and their tests together (context ability + current_timestamp function + timezone stuff + DATE fixes). |
3861c88
to
6c64814
Compare
Added support for context parameters specified as JDBC connection properties or a JSON object for SQL-over-JSON-over-HTTP. Also added features that depend on context functionality: - Added CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP functions. - Added support for time zones other than UTC via a "timeZone" context. - Pass down query context to Druid queries too. Also some bug fixes: - Fix DATE handling, it was largely done incorrectly before. - Fix CAST(__time TO DATE) which should do a floor-to-day. - Fix non-equality comparisons to FLOOR(__time TO X). - Fix maxQueryCount property.
6c64814
to
a461c12
Compare
Merged with master to pick up changes from #3838. |
👍 |
looks good so far, will take another look after conflict fix |
thx for the review @jon-wei, pushed a fix for conflicts. |
👍 |
Added support for context parameters specified as JDBC connection properties
or a JSON object for SQL-over-JSON-over-HTTP.
Also added features that depend on context functionality:
Also some bug fixes: