We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
feast apply
Calling feast apply multiple time on the same feature repo with MySQL online store should not throw an error.
Calling feast apply attempts to create table index even if the index exists. It throw MySQL duplicate key error if the index already exists.
Add a check to the existence of the index before index creation
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Expected Behavior
Calling
feast apply
multiple time on the same feature repo with MySQL online store should not throw an error.Current Behavior
Calling
feast apply
attempts to create table index even if the index exists. It throw MySQL duplicate key error if the index already exists.Steps to reproduce
feast apply
first time will create table(s) and index(es) on the MySQL database.feast apply
again will throw duplicate key error.Specifications
Possible Solution
Add a check to the existence of the index before index creation
The text was updated successfully, but these errors were encountered: