alibaba/GraphScope

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

Open

#2,938 opened on Jun 27, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)HTML (301 forks)batch import
component:dev-infracomponent:giegood first issuejavapriority:high

Repository metrics

Stars
 (2,401 stars)
PR merge metrics
 (Avg merge 1m) (7 merged PRs in 30d)

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

Research direction
Investigate the Maven assembly plugin configuration to use jar with dependencies and identify which dependencies are bloating the wheel. Check if there is a way to exclude transitive dependencies from Neo4j that are not needed.
Tech stack
javapython
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaMavenPython packaging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60