Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Subtask] Build catalog-lakehouse dependent JAR into catalogs directory #391

Closed
Tracked by #321
xunliu opened this issue Sep 13, 2023 · 0 comments · Fixed by #394
Closed
Tracked by #321

[Subtask] Build catalog-lakehouse dependent JAR into catalogs directory #391

xunliu opened this issue Sep 13, 2023 · 0 comments · Fixed by #394
Assignees

Comments

@xunliu
Copy link
Member

xunliu commented Sep 13, 2023

Describe the subtask

Currently, building catalog-lakehouse module can't move dependent JAR into ${graviton}/distribution/package/catalogs/.
It may be in conflict with Graviton.

New distribution directory struct is :

├── bin
├── conf
└── distribution/package
    ├── bin/
    ├── catalogs/hive/libs
    ├── catalogs/lakehouse/libs
    ├── conf/
    └── libs/

Parent issue

#321

@xunliu xunliu self-assigned this Sep 13, 2023
jerryshao pushed a commit that referenced this issue Sep 14, 2023
… into catalogs directory (#394)

### What changes were proposed in this pull request?

+ Added `catalog-lakehouse` job in the Gradle build scripts.
+ Use better names for some jobs


```
├── bin
├── conf
└── distribution/package
    ├── bin/
    ├── catalogs/hive/libs
    ├── catalogs/lakehouse/libs
    ├── conf/
    └── libs/
```

### Why are the changes needed?

Currently, building `catalog-lakehouse` module can't move dependent JAR
into `${graviton}/distribution/package/catalogs/`. It may be in conflict
with Graviton.

Fix: #391 

### Does this PR introduce _any_ user-facing change?

N/A

### How was this patch tested?

CI passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant