-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
add a Java wrapper for datafusion #1108
Comments
maybe related apache/arrow#11067 |
In general I am somewhat down on adding more integration tests into the core DataFusion repo as each type of integration added makes any PR in the core that much more complicated and there are more possibilities for flakytests in some infrastructural components that we may/may not be familiar with What would you think about implementing this as its own crate / in its own repo? That would also allow initial revisions to be iterated on / released faster than if it is in the arrow-datafusion repo and under ASF governance? |
Agree that this can be in a separate repo. Let me still keep this open for some feedback collections |
I agree this could be done better in a separate repo. |
it looks like everyone is having mono repo PTSD here :D |
for the moment let me put this here, once ready i can transfer it under apache org |
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A challenge to add a Java wrapper for datafusion, so that we can leverage Rust's speed and memory management and also Java's eco-system.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Unlike Python where we have
maturin
- an easy to use binding to Rust, I'm trying to use JNI in this case but that requires handling memory on/off heap. One way to achieve this is to leverage Arrow's IPC between Java and Rust.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: