-
Notifications
You must be signed in to change notification settings - Fork 334
Using Arrow Date32 format to transfer LocalDate across JVMs
#14632
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
| offheapBuffer = buf; | ||
| validitySet = new ImmutableBitSet(validity, data.length); | ||
| } | ||
| if (offheapBuffer == null && getType() instanceof DateType) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdunkerley, it would be more efficient if the DateBuilder was creating a specialized storage backed by ByteBuffer rather than converting LocalDate[] into the ByteBuffer when requested. We'd be allocating way less objects by doing so...
std-bits/tests/src/test/java/org/enso/base/polyglot/tests/DateStorageTest.java
Show resolved
Hide resolved
std-bits/tests/src/test/java/org/enso/base/polyglot/tests/DateStorageTest.java
Show resolved
Hide resolved
|
Jaroslav Tulach reports a new STANDUP for yesterday (2026-01-14): Progress: .
|
Pull Request Description
in dual JVM (mock) mode:
ByteBufferto allow dual JVM buffer exchange #14309Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Java,