Skip to content

GH-477: Fix Flight JDBC DATE(MILLISECOND) parameter binding#1219

Open
yujin5701 wants to merge 1 commit into
apache:mainfrom
yujin5701:codex/gh-477-date-milli-binding
Open

GH-477: Fix Flight JDBC DATE(MILLISECOND) parameter binding#1219
yujin5701 wants to merge 1 commit into
apache:mainfrom
yujin5701:codex/gh-477-date-milli-binding

Conversation

@yujin5701

Copy link
Copy Markdown

What's Changed

This fixes Flight JDBC prepared statement binding for Arrow DATE(MILLISECOND)
parameters.

Avatica represents JDBC DATE values as days since the Unix epoch. The Flight
JDBC parameter binder already writes that value correctly for DateDayVector,
but it was also writing the same day value directly into DateMilliVector,
which expects milliseconds since the Unix epoch.

This now converts epoch days to epoch milliseconds before writing to
DateMilliVector.

Tested with ArrowFlightPreparedStatementTest.

Closes #477.

@github-actions

This comment has been minimized.

@lidavidm lidavidm added the bug-fix PRs that fix a big. label Jul 8, 2026
@github-actions github-actions Bot added this to the 20.0.0 milestone Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug-fix PRs that fix a big.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flight JDBC Driver not setting parameter correctly when parameter type is DATE<MILLISECOND>

2 participants