Skip to content

Conversation

@jhmannok
Copy link
Owner

@jhmannok jhmannok commented Jul 6, 2023

Made PR to make reviewing changes more convenient

jhmannok added 6 commits July 5, 2023 15:18
 - Old behaviour treats the calendar object passed into the corresponding methods to be the timezone to convert the data into, which is incorrect according to what is defined in the JDBC API
 - Fixed: Correct behaviour is that the calendar object is used to extend the data into the timezone of the calendar object, essentially asserting that the data is at the timezone defined in the calendar object
 - Fixed: for vectors that do store timezone information (ie. TimestampVector), the getter methods will use the timezone defined in vector as the timezone assertion and ignores the calendar object if one was passed in
…Test

- Made timezone converting logic more readable in ArrowFlightJdbcTimeStampVectorAccessor
- Fixed checkstyle issues
- Refactored getTimestampForVector() to be more concise and readable
…one an if statement and changed all nonNull usage to compare with null explicitly

ArrowFlightJdbcTimeStampVectorAccessorTest: Modified test so system timezone is compared more explicitly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants