[Release] arrow-java-root-18.3.0-source-release.zip includes JNI binaries

Open
#743 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
release

Research direction

Start with the v18.3.0-rc2 source-release.zip and inspect how its jni/ and testing/ directories are assembled. Determine whether JNI binaries and testing/ belong in the source archive, then verify the resulting archive no longer includes the unwanted binaries and remains a valid source release.

Written by the indexing model from the issue text.

Description

Type: bug
Describe the bug, including details regarding any error messages, version, and platform.

This is not a release blocker.

https://github.com/apache/arrow-java/releases/download/v18.3.0-rc2/arrow-java-root-18.3.0-source-release.zip

JNI binaries are large. Can we remove them from source-release.zip?

$ LANG=C du -hsc arrow-java-root-18.3.0/jni/*
236K	arrow-java-root-18.3.0/jni/arrow_cdata_jni/
272M	arrow-java-root-18.3.0/jni/arrow_dataset_jni/
156M	arrow-java-root-18.3.0/jni/arrow_orc_jni/
444M	arrow-java-root-18.3.0/jni/gandiva_jni/
871M	total

source-release.zip also has testing/. It's not so large but should we remove it? Or should we keep it?

$ LANG=C du -hsc arrow-java-root-18.3.0/testing
8.8M	arrow-java-root-18.3.0/testing
8.8M	total
Dominant language
Java
Stars
95
Forks
154
Avg merge
2d 10h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-java

All issues in apache/arrow-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.