[
https://issues.apache.org/jira/browse/ARROW-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15196762#comment-15196762
]
Dan Robinson commented on ARROW-55:
---
See patch (fixing tests, not adding to Travis)
Having thought about this quite a bit in the past, I think the mechanics of
how to share memory are by far the easiest part. The much harder part is
the resource management and ownership. Questions like:
- if you are using an mmapped file in /dev/shm/, how do you make sure it
gets cleaned up if
@Corey
The POC Steven and Wes are working on is based on MappedBuffer but I'm
looking at using netty's fork of tcnative to use shared memory directly.
@Yiannis
We need to have both RPC and a shared memory mechanisms (what I'm inclined
to call IPC but is a specific kind of IPC). The idea is we
I was seeing Netty's unsafe classes being used here, not mapped byte
buffer not sure if that statement is completely correct but I'll have to
dog through the code again to figure that out.
The more I was looking at unsafe, it makes sense why that would be
used.apparently it's also supposed to be
Hi Wes,
can you please clarify something I don't understand? The next versions of
arrow will include the shared memory control flow as well?
So then, what is needed for HBase (for instance) to be integrated is the
adapter to the arrow format?
If yes, then who will be responsible for keeping the
[
https://issues.apache.org/jira/browse/ARROW-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15195349#comment-15195349
]
Uwe L. Korn commented on ARROW-65:
--
Probably best is to sync both files as good as possible. On Linux, I
[
https://issues.apache.org/jira/browse/ARROW-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qian Xu updated ARROW-66:
-
Attachment: ARROW-66.patch
Add a minimal cmake version prompt in readme
> Maybe some missing steps in installation
