alibaba / alibaba/GraphScope

[BUG] Use jar-with-dependencies to package frontend artifacts in GIE

Open
#2,938 1 comment 0 reactions 0 assignees View on GitHub
component:dev-infra component:gie good first issue java priority:high
Dominant language
C++
Stars
3.6k
Forks
468
Avg merge
29m
Merged PRs (30d)
1

Description

**Describe the bug**

It is quite superised that we didn't use `jar-with-dependency` to package the release artifacts for java. Recent changes about neo4j introduced some new jar dependency, double the size of the wheel package (https://pypi.org/project/graphscope/0.23.0a20230625/#files), makes graphscope hard to install with python ....

**Expected Outcome**

The ultimate goal is to reduce the size of wheels, which in this issue, is the artifacts of interactive engine. You could observe the size of artifacts of gie by `make interactive` and find `graphscope.tar.gz` within `interactive_engine/assembly/target`

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Research direction

Start with the interactive_engine assembly packaging configuration and run `make interactive` to inspect `interactive_engine/assembly/target/graphscope.tar.gz`. Trace how the GIE Java release artifacts and their dependencies are bundled, then verify that the resulting wheel artifacts are smaller without losing required dependencies.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, neo4j, python
Domain
build-system, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.