apache / apache/arrow-java

[Java] Include compiled Flatbuffers sources in release artifacts

Open
#293 0 comments 0 reactions 0 assignees View on GitHub
Type: bug
Dominant language
Java
Stars
94
Forks
152
Avg merge
3d 16h
Merged PRs (30d)
11

Description

I'm seeing the flatc that's available in Maven foul up users because it depends on a version of glibc (2.14) which is too new for many enterprise Linux users. It would be better for the Arrow Java artifacts to not depend on flatc at all, if possible.

We could check the compiled sources into source control, but that seems less than ideal. Is there a clean way bundle them at packaging time?

**Reporter**: [Wes McKinney](https://issues.apache.org/jira/browse/ARROW-397) / @wesm

**Note**: *This issue was originally created as [ARROW-397](https://issues.apache.org/jira/browse/ARROW-397). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the migration documentation linked in the issue and the Maven packaging setup for the Arrow Java artifacts. Confirm how flatc is currently involved and define a packaging-time path for including compiled FlatBuffers sources without requiring flatc at use time; done means the release artifacts no longer depend on that binary for these sources.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.