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

[FEATURE] Error message is not meaning full, "Fail to run query, cause: Failed to refresh Flint index" #201

Closed
Tracked by #281
penghuo opened this issue Dec 18, 2023 · 2 comments
Labels
0.3 maintenance Code refactoring

Comments

@penghuo
Copy link
Collaborator

penghuo commented Dec 18, 2023

Is your feature request related to a problem?
In Spark log, when refresh index, error message is.

23/12/18 14:33:30 ERROR FlintSpark: Failed to refresh Flint index
java.lang.IllegalStateException: Transaction failed due to initial log precondition not satisfied

But, error message exposed by FlintJob is

Fail to run query, cause: Failed to refresh Flint index

What solution would you like?
Clearly expose error message, e.g.

drop index before refresh index.

What alternatives have you considered?
No.

@penghuo
Copy link
Collaborator Author

penghuo commented Mar 8, 2024

another case,

Lack s3 checkpoint write permission, create index failed, but error message is "Fail to run query, cause: Failed to refresh Flint index"

@noCharger
Copy link
Collaborator

Found a similar issue. If no one is working on, I can take this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.3 maintenance Code refactoring
Development

No branches or pull requests

3 participants