[
https://issues.apache.org/jira/browse/ARROW-11135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318952#comment-17318952
]
Kouhei Sutou commented on ARROW-11135:
--------------------------------------
I don't agree with the former.
I agree with the latter.
{{libgandiva_jni}} should not depend on other libraries (should be linked with
other libraries statically). Could you try .jar at
https://github.com/ursacomputing/crossbow/releases/tag/nightly-2021-04-09-0-github-gandiva-jar-osx
?
We need to improve our release process to resolve them. The current our release
process generates Java packages on release manager's environment:
https://github.com/apache/arrow/blob/master/dev/release/01-perform.sh
The release manager for 3.0.0 used macOS. So arrow-gandiva 3.0.0 works only on
macOS.
We should build arrow-gandiva and native libraries (for macOS, Linux and
Windows) for it on CI (we can use macOS, Linux and Windows on CI) and collect
native libraries for all supported platforms into one arrow-gandiva.jar. Our
release process should just pushes the built arrow-gandiva.jar instead of
building arrow-gandiva.ja on release manager's machine.
We'll release 4.0.0 soon. This improvement will not be included in 4.0.0 if no
volunteers that work on this soon.
> Using Maven Central artifacts as dependencies produce runtime errors
> --------------------------------------------------------------------
>
> Key: ARROW-11135
> URL: https://issues.apache.org/jira/browse/ARROW-11135
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.0.0, 3.0.0
> Reporter: Michael Mior
> Priority: Major
>
> I'm working on connecting Arrow/Gandiva with Apache Calcite. Overall the
> integration is working well, but I'm having issues . As [suggested on the
> mailing
> list|https://lists.apache.org/thread.html/r93a4fedb499c746917ab8d62cf5a8db8c93a7f24bc9fac81f90bedaa%40%3Cuser.arrow.apache.org%3E],
> using Dremio's public artifacts solves the problem. Between two Apache
> projects however, there would be strong preference to use Apache artifacts as
> a dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
