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
For some reason our system need to set netty param io.netty.noUnsafe=true. We have replaced arrow-memory-netty with arrow-memory-unsafe. But there are still some utils in arrow-vector like DictionaryEecoder, VectorSchemaRootAppender using PlatformDependent which will cause NullPointerException when io.netty.noUnsafe=true .
IMO netty params should not affect the work of arrow-vector, can we replace the usage of PlatformDependent by ArrowBuf#setxxx ?
Component(s)
Java
The text was updated successfully, but these errors were encountered:
gf2121
changed the title
[Java] No more usage of PlatformDependent in arrow-vector
[Java] Remove usage of PlatformDependent in arrow-vector
Dec 11, 2022
…tor, arrow-jdbc and arrow-algorithm (apache#14913)
* Closes: apache#14912
Authored-by: 郭峰 <guofeng.my@bytedance.com>
Signed-off-by: David Li <li.davidm96@gmail.com>
…tor, arrow-jdbc and arrow-algorithm (apache#14913)
* Closes: apache#14912
Authored-by: 郭峰 <guofeng.my@bytedance.com>
Signed-off-by: David Li <li.davidm96@gmail.com>
fatemehp
pushed a commit
to fatemehp/arrow
that referenced
this issue
Feb 24, 2023
…tor, arrow-jdbc and arrow-algorithm (apache#14913)
* Closes: apache#14912
Authored-by: 郭峰 <guofeng.my@bytedance.com>
Signed-off-by: David Li <li.davidm96@gmail.com>
Describe the enhancement requested
For some reason our system need to set netty param
io.netty.noUnsafe=true
. We have replacedarrow-memory-netty
witharrow-memory-unsafe
. But there are still some utils inarrow-vector
likeDictionaryEecoder
,VectorSchemaRootAppender
usingPlatformDependent
which will causeNullPointerException
whenio.netty.noUnsafe=true
.IMO netty params should not affect the work of
arrow-vector
, can we replace the usage ofPlatformDependent
byArrowBuf#setxxx
?Component(s)
Java
The text was updated successfully, but these errors were encountered: