-
Notifications
You must be signed in to change notification settings - Fork 9
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
need floor before Int64 #80
Conversation
Codecov Report
@@ Coverage Diff @@
## master #80 +/- ##
=========================================
+ Coverage 23.7% 85.5% +61.7%
=========================================
Files 11 6 -5
Lines 2563 221 -2342
=========================================
- Hits 609 189 -420
+ Misses 1954 32 -1922 Continue to review full report at Codecov.
|
Thanks for checking out the package @snthot! Can you provide a brief example that demonstrates the error you saw? Prior to this fix, the test suite passed with this functionality, so I want to make sure I'm accounting for any edge cases that might be present. |
oh sure, here is the case:
I noticed that your test pass because the DateTime data are defined down to second(s) level but the now() function normally go down to millisecond level so I got the trouble. And this prevented me from using 'load_table_binary_columnar' function. Once I fixed this problem by applying 'floor' I found that I can convert high precision datetime to TColumn (with losses) and load the data to OmniSci correctly. I am not sure whether there is a better way to fix this. But it looks like Omnisci supports high precision timestamp so you may go with Float64 instead of Int64 ? |
@snthot Thanks for the example, yes that's an oversight on my part. Your solution fixes the timestamp at the seconds level (which is what OmniSci supported when I implemented this), but it's a good question about how to implement higher-resolution timestamps |
I confirmed internally that we do want to cast to Int. Could you make your change Separately, I'll open up an issue about supporting high-resolution timestamps. Thanks! |
great! I absolutely agree! |
I worked on Julia Version 1.2.0 (2019-08-20) with omnisci/core-os-cpu docker.
I bumped into trouble when applying TColumn on Datetime column.
I think we need "floor" before converting into Int64 and it works well.
No obligation, just want to have it worked well :-)