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] Separate two Java clients, one for Admin to manage metalake, the other for normal catalog operations #2478

Closed
Tracked by #2418
shaofengshi opened this issue Mar 8, 2024 · 0 comments · Fixed by #2483
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@shaofengshi
Copy link
Contributor

Describe the subtask

Today in the Java client, the "GravitinoClient" has all the operations for metalakes, including list, create, alter and drop, etc. That is mostly for the system administrator's operation, not friendly for a normal user. Normal user mainly works on catalogs. So I would separate the Java client into two, one is "GravitinoAdminClient" which similar to as-is version; the other is "GravitinoClient" which has a "metalake_name" as input parametor, and then user mainly works on catalogs.

Parent issue

#2418

@shaofengshi shaofengshi added the subtask Subtasks of umbrella issue label Mar 8, 2024
@shaofengshi shaofengshi self-assigned this Mar 8, 2024
@shaofengshi shaofengshi added this to the Gravitino 0.5.0 milestone Mar 8, 2024
shaofengshi added a commit to shaofengshi/gravitino that referenced this issue Mar 8, 2024
jerryshao pushed a commit that referenced this issue Mar 17, 2024
… normal user (#2483)

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

Separate the current Java client into two, one is "GravitinoAdminClient"
which similar to as-is version; the other is "GravitinoClient" which has
a "metalake_name" as input parametor, and then user mainly works on
catalogs.

### Why are the changes needed?

Today in the Java client, the "GravitinoClient" has all the operations
for metalakes, including list, create, alter and drop, etc. That is
mostly for the system administrator's operation, not friendly for a
normal user. Normal user mainly works on catalogs.

Fix: #2478

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

Yes, the Java client "GravitinoClient.java" has user interface change;
If the user want to operate Metalake, he can switch to use the
"GravitinoAdminClient.java".

### How was this patch tested?

The UT for the GravitinoClient can ensure the function is not broken.
coolderli pushed a commit to coolderli/gravitino that referenced this issue Apr 2, 2024
…in and normal user (apache#2483)

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

Separate the current Java client into two, one is "GravitinoAdminClient"
which similar to as-is version; the other is "GravitinoClient" which has
a "metalake_name" as input parametor, and then user mainly works on
catalogs.

### Why are the changes needed?

Today in the Java client, the "GravitinoClient" has all the operations
for metalakes, including list, create, alter and drop, etc. That is
mostly for the system administrator's operation, not friendly for a
normal user. Normal user mainly works on catalogs.

Fix: apache#2478

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

Yes, the Java client "GravitinoClient.java" has user interface change;
If the user want to operate Metalake, he can switch to use the
"GravitinoAdminClient.java".

### How was this patch tested?

The UT for the GravitinoClient can ensure the function is not broken.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subtask Subtasks of umbrella issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant