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] TrinoContainer#checkSyncCatalogFromGravitino will always return false #3237

Closed
xiaozcy opened this issue Apr 30, 2024 · 1 comment · Fixed by #3238
Closed

[Bug report] TrinoContainer#checkSyncCatalogFromGravitino will always return false #3237

xiaozcy opened this issue Apr 30, 2024 · 1 comment · Fixed by #3238
Assignees
Labels
bug Something isn't working

Comments

@xiaozcy
Copy link
Contributor

xiaozcy commented Apr 30, 2024

Version

main branch

Describe what's wrong

In #2433 , we use simple catalog name in Trino connector. In that case, when we execute SHOW CATALOGS in Trino, it returns the original catalog names in Trino (without {metalake}. prefix).

But in com.datastrato.gravitino.integration.test.container.TrinoContainer#checkSyncCatalogFromGravitino, we use format("SHOW CATALOGS LIKE '%s.%s'", metalakeName, catalogName) to match the result of the execution, which means this method will always return false. Besides, we never verify the return value of this method where it is called, so the current test can still be executed successfully.

Error message and/or stacktrace

N/A

How to reproduce

Use format("SHOW CATALOGS LIKE '%s'", catalogName) instead, and verify the return value of this method where it is called.

Additional context

No response

@xiaozcy xiaozcy added the bug Something isn't working label Apr 30, 2024
@xiaozcy xiaozcy changed the title [Bug report] TrinoContainer#checkSyncCatalogFromGravitino will always return false [Bug report] TrinoContainer#checkSyncCatalogFromGravitino will always return false Apr 30, 2024
yuqi1129 pushed a commit that referenced this issue May 1, 2024
### What changes were proposed in this pull request?

use simple catalog name in
`com.datastrato.gravitino.integration.test.container.TrinoContainer#checkSyncCatalogFromGravitino`,
and verify it where it is called.

### Why are the changes needed?

Fix: #3237 

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

N/A

### How was this patch tested?

ITs

---------

Co-authored-by: zhanghan18 <[email protected]>
github-actions bot pushed a commit that referenced this issue May 1, 2024
### What changes were proposed in this pull request?

use simple catalog name in
`com.datastrato.gravitino.integration.test.container.TrinoContainer#checkSyncCatalogFromGravitino`,
and verify it where it is called.

### Why are the changes needed?

Fix: #3237 

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

N/A

### How was this patch tested?

ITs

---------

Co-authored-by: zhanghan18 <[email protected]>
@yuqi1129
Copy link
Contributor

yuqi1129 commented May 1, 2024

@xiaozcy
Thanks for your contribution.

diqiu50 pushed a commit to diqiu50/gravitino that referenced this issue Jun 13, 2024
…pache#3238)

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

use simple catalog name in
`com.datastrato.gravitino.integration.test.container.TrinoContainer#checkSyncCatalogFromGravitino`,
and verify it where it is called.

### Why are the changes needed?

Fix: apache#3237 

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

N/A

### How was this patch tested?

ITs

---------

Co-authored-by: zhanghan18 <[email protected]>
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.

2 participants