- Notifications
You must be signed in to change notification settings - Fork 310
DATACASS-694 - Fix LocalTime conversion #166
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
Conversation
| @hurelhuyag Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
| @hurelhuyag Thank you for signing the Contributor License Agreement! |
| Care to add an integration test to |
| Read and Write test will work fine. Not needed to add more. Only way to check that is use cqlsh |
| We have existing tests that prove that read and write of Previously, the representation in Cassandra ( |
| On the other hand datastax documented time datatype is nanoseconds not milliseconds.
|
| And Cassandra
|
| And I'm not sure this kind of test is needed or not |
| @hurelhuyag it is needed to prevent that this type of bug comes again. |
| 2 integration test added |
LocalTime now correctly uses nanoseconds. Original pull request: #166.
Add author tags. Reformat code. Adapt remaining tests. Original pull request: #166.
LocalTime now correctly uses nanoseconds. Original pull request: #166.
Add author tags. Reformat code. Adapt remaining tests. Original pull request: #166.
LocalTime now correctly uses nanoseconds. Original pull request: #166.
Add author tags. Reformat code. Adapt remaining tests. Original pull request: #166.
| Thanks a lot for your contribution. That's squashed, merged, polished, and backported now. |
java.time.LocalTime to Cassandra time datatype mapping fix