-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
ESQL Date Nanos Addition and Subtraction #116839
Changes from all commits
cf6705c
15c5d3a
07cdbf6
352cda8
bd71603
cb0baca
f3e031e
e9ec7a8
aa1ef87
2dddb42
a69c9a5
f6fc138
9c3a9df
dff58a0
bb16502
1ba6378
35fdb06
95806b7
f5b41aa
0fbead2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered adding
DATE_NANOS
toisDateTime
, but that creates a few problems. First off, we useisDateTime
in a lot of places, and touching all of them would have made this already quite large PR even larger. Second, there are clearly some places, such asEsqlDataTypeConverter
which clearly need to check for exactlyDATETIME
type, and would have incorrect behavior if we expandedisDateTime
to includeDATE_NANOS
. Given that, it seemed like adding a new function was the safest way to proceed.