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

1. Add MySQL online store to the feature repo
2. Calling feast apply first time will create table(s) and index(es) on the MySQL database.
3. Calling feast apply again will throw duplicate key error.

Specifications

• Version: master branch
• Platform:
• Subsystem:

Possible Solution

Add a check to the existence of the index before index creation