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

[Bug report] fileset API is not correct in openapi.yml #2618

Closed
jerryshao opened this issue Mar 20, 2024 · 0 comments · Fixed by #2619
Closed

[Bug report] fileset API is not correct in openapi.yml #2618

jerryshao opened this issue Mar 20, 2024 · 0 comments · Fixed by #2619
Assignees
Labels
bug Something isn't working

Comments

@jerryshao
Copy link
Contributor

Version

main branch

Describe what's wrong

In openapi filesets.yml file, both Fileset and FilesetCreateRequest interfaces have one more field "description", which is not correct.

Error message and/or stacktrace

image

How to reproduce

We should remove this field.

Additional context

No response

@jerryshao jerryshao added the bug Something isn't working label Mar 20, 2024
@jerryshao jerryshao added this to the Gravitino 0.5.0 milestone Mar 20, 2024
@jerryshao jerryshao self-assigned this Mar 20, 2024
mchades pushed a commit that referenced this issue Mar 21, 2024
)

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

Remove the "description" field in Fileset related APIs.

### Why are the changes needed?

Because the `description` field does not exist in the related APIs, it
should be removed, otherwise, it will lead to an issue.

Fix: #2618 

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

No.

### How was this patch tested?

Manually verification.
coolderli pushed a commit to coolderli/gravitino that referenced this issue Apr 2, 2024
…oc (apache#2619)

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

Remove the "description" field in Fileset related APIs.

### Why are the changes needed?

Because the `description` field does not exist in the related APIs, it
should be removed, otherwise, it will lead to an issue.

Fix: apache#2618 

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

No.

### How was this patch tested?

Manually verification.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant