You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sender has no dateColumn() setter for DATE columns #83
Sender has no dateColumn() setter, so a Java producer cannot write a DATE column — even though the server accepts DATE on QWP ingress and this client reads it back fine on egress.
The long overload mirrors the other clients' wire-level form; the Instant overload matches how timestampColumn(name, Instant) already reads at the call site. As with every other column, a null is written by omitting the setter before at() / atNow().
Worth confirming the intended truncation behaviour for the Instant overload, since DATE is millisecond-resolution and Instant is not — silently truncating sub-millisecond precision versus rejecting it is a deliberate choice, and the other clients sidestep it by only accepting millis (except Go, which takes a time.Time).
@nwoolmer Hi! I'd like to work on this issue. I can update the Docker deployment documentation with the required daemon.json / ulimit configuration and add the relevant explanation. Could you please assign this issue to me?
Activity
dhruv-creates69 commentedon Sep 29, 2026
@nwoolmer Hi! I'd like to work on this issue. I can update the Docker deployment documentation with the required
daemon.json/ ulimit configuration and add the relevant explanation. Could you please assign this issue to me?