arrow-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacques Nadeau <jacq...@apache.org>
Subject Re: [Java] Issues with "Split Packages" and OSGi (and probably Java 9+)
Date Mon, 24 Aug 2020 22:03:38 GMT
I suggest renaming the vector related util package to
org.apache.arrow.vector.util and memory to org.apache.arrow.memory.util. It
would be great if you could open a ticket and propose a patch (assuming
others agree with the solution).

On Mon, Aug 24, 2020 at 2:53 PM Bernd Wiswedel <bernd.wiswedel@knime.com>
wrote:

>
> We at KNIME (https://www.knime.com/) are currently looking at Arrow as an
> alternative data representation. Our platform is based on Eclipse and uses
> OSGi for dependency management. As part of that we use the Arrow artifacts
> available from maven and convert them to OSGI bundles.
>
> We noticed that at least one java package (org.apache.arrow.util) is
> provided in two different artifacts
>
>    - arrow-memory-core: (Link to GitHub
>    <https://github.com/apache/arrow/tree/master/java/memory/memory-core/src/main/java/org/apache/arrow/util>
>    )
>    - arrow-vectors: (Link to GitHub
>    <https://github.com/apache/arrow/tree/master/java/vector/src/main/java/org/apache/arrow/util>
>    )
>
> This is causing us trouble as the package is available via two chains. I
> believe this is also going to be troublesome once it's used in a Java 9+
> environment where different modules(*) can't share the same package ('split
> package' -- some more details are here
> <https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html>
> ).
>
> The simplest solution is to move classes from one package to the other
> (same) package. If that's not an accepted option it could also be moved
> into a new artifact(*) arrow-util or so.
>
> Please advise!
>
> Thanks,
>  Bernd
>
> (*) Bundle, Module, Plug-In, Artefact ... different terms used in
> different contexts but they mostly mean the same thing.
>

Mime
View raw message