You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Kouhei Sutou (Jira)" <ji...@apache.org> on 2022/07/06 07:41:00 UTC

[jira] [Comment Edited] (ARROW-15174) [Java] Consolidate JNI compilation

    [ https://issues.apache.org/jira/browse/ARROW-15174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537634#comment-17537634 ] 

Kouhei Sutou edited comment on ARROW-15174 at 7/6/22 7:40 AM:
--------------------------------------------------------------

Note that the is a new JNI interface (to datafusion) that does not use the c-data-interface.  (and, incidentally, also takes a different approach to  packaging the native binaries in Maven than the other JNI interfaces).

See: [https://lists.apache.org/thread/6h1mry3n3fb2omf3o24dzbf0n9rhs51h] for the archive thread.

Announcement email below: 

Hi dev@arrow,

Recently I've created and published a Java binding[1] to datafusion[2],
as part of datafusion-contrib projects[3]. I've updated the README.md[4]
so people can pick it up via maven[5] or gradle.

Any feedback or contributions are welcome!

[1]: [https://github.com/datafusion-contrib/datafusion-java]
[2]: [https://github.com/apache/arrow-datafusion]
[3]: [https://github.com/datafusion-contrib]
[4]: [https://github.com/datafusion-contrib/datafusion-]
java/blob/main/README.md
[5]: [https://repo.maven.apache.org/maven2/io/github/datafusion-]
contrib/datafusion-java/


was (Author: ljw1001):
Note that the is a new JNI interface (to datafusion) that does not use the c-data-interface.  (and, incidentally, also takes a different approach to  packaging the native binaries in Maven than the other JNI interfaces).

See: [https://lists.apache.org/list.html?dev@arrow.apache.org] for the archive thread.

Announcement email below: 

Hi dev@arrow,

Recently I've created and published a Java binding[1] to datafusion[2],
as part of datafusion-contrib projects[3]. I've updated the README.md[4]
so people can pick it up via maven[5] or gradle.

Any feedback or contributions are welcome!

[1]: [https://github.com/datafusion-contrib/datafusion-java]
[2]: [https://github.com/apache/arrow-datafusion]
[3]: [https://github.com/datafusion-contrib]
[4]: [https://github.com/datafusion-contrib/datafusion-]
java/blob/main/README.md
[5]: [https://repo.maven.apache.org/maven2/io/github/datafusion-]
contrib/datafusion-java/

> [Java] Consolidate JNI compilation
> ----------------------------------
>
>                 Key: ARROW-15174
>                 URL: https://issues.apache.org/jira/browse/ARROW-15174
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Alessandro Molina
>            Assignee: Larry White
>            Priority: Major
>             Fix For: 9.0.0
>
>
> *Umbrella ticket for consolidating Java JNI compilation initiative*
> Seems we have spread the JNI code across the {{cpp}} and {{java}} directories. As for other bindings (Python) we already discussed it would be great to consolidate and move all cpp code related to PYthon into PyArrow, we should do something equivalent for Java too and move all C++ code specific to Java into the Java project.
> At the moment there are two JNI related directories:
>  * [https://github.com/apache/arrow/tree/master/java/c]
>  * [https://github.com/apache/arrow/tree/master/cpp/src/jni]
> Let's also research what's the best method to build those. The {{java/c}} directory seems to be already integrated with the Java build process, let's check if that approach is something we can reuse for the {{dataset}} directory too



--
This message was sent by Atlassian Jira
(v8.20.10#820010)