-
Notifications
You must be signed in to change notification settings - Fork 209
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
datetime
objects in row_filter
expressions are not casted and raise an error
#1456
Comments
Thanks for reporting this issue! iceberg-python/pyiceberg/expressions/literals.py Lines 122 to 149 in dbcf65b
Looks like we don't take into account python's cc @Fokko do you have context around this? |
Any thoughts here? there are a few ways to implement this from what I can tell, the easiest would be to just add a clause to the |
@jayceslesar |
@jayceslesar i think that makes sense. Are you interested to contribute this? |
Happy to contribute, was just wondering if there was a slightly prettier way but if that is acceptable than sounds good to me |
I think We use iceberg-python/pyiceberg/expressions/literals.py Lines 570 to 576 in b15934d
cc @Fokko wdyt? |
Feature Request / Improvement
in the following
row_filter
in ascan()
call,the
start_time
andend_time
variables aredatetime
objects. When running ascan
with thatrow_filter
I end up with the error ofInstead, the expressions should correctly cast the
datetime
object instead of expecting anisoformat
string, which is the current behaviorThe text was updated successfully, but these errors were encountered: