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

Projjal Chanda commented on ARROW-11135:
----------------------------------------

[~julianhyde]  The gandiva lib in ursa-labs nightly mac and linux jars are 
built with static protobuf dependency (see 
[here|https://github.com/apache/arrow/blob/7c4a07eeddf885189f7a6ad01ba9f98945bfa022/dev/tasks/gandiva-jars/build-cpp-osx.sh#L39]
 and 
[here)|https://github.com/apache/arrow/blob/7c4a07eeddf885189f7a6ad01ba9f98945bfa022/dev/tasks/gandiva-jars/build-cpp-linux.sh#L45].
 It seems the [release gandiva 
jar|https://github.com/apache/arrow/blob/7c4a07eeddf885189f7a6ad01ba9f98945bfa022/dev/release/post-11-java.sh#L45]
 is not build similarly, and the supported platform for the released gandiva 
jar depends on the release manager's machine.

Agree with [~kou] about the changes needed on gandiva release process. We need 
to -

1. Build arrow-gandiva and native libraries in all supported platforms and 
collect all the libraries in a single jar (Currently we create separate jars 
for macos and linux)
2. Release process should push the built arrow-gandiva jar instead of building 
it on RM's machine.

I will try to get this done.

 

 

 

> 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)

Reply via email to