Skip to content
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

Closed
jimexist opened this issue Oct 12, 2021 · 6 comments
Closed

add a Java wrapper for datafusion #1108

jimexist opened this issue Oct 12, 2021 · 6 comments
Labels
enhancement New feature or request

Comments

@jimexist
Copy link
Member

jimexist commented Oct 12, 2021

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.

@jimexist jimexist added the enhancement New feature or request label Oct 12, 2021
@jimexist
Copy link
Member Author

maybe related apache/arrow#11067

@alamb
Copy link
Contributor

alamb commented Oct 12, 2021

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?

@jimexist
Copy link
Member Author

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

@Dandandan
Copy link
Contributor

I agree this could be done better in a separate repo.
If it's mature enough to be considered in the repository, we can decide to do so.

@houqp
Copy link
Member

houqp commented Oct 13, 2021

it looks like everyone is having mono repo PTSD here :D

@jimexist
Copy link
Member Author

for the moment let me put this here, once ready i can transfer it under apache org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants