3a765079db
# 🔍 Description ## Issue References 🔗 This pull request is a small fix for #5674 ## Describe Your Solution 🔧 PostgreSQL support as backend for metadata store was added in #6027. If we choose it and run schema init scripts several times, then the following errors will be logged: `Error executing sql: CREATE UNIQUE INDEX unique_identifier_index ON metadata(identifier), with params: . ERROR: relation "unique_identifier_index" already exists`. This PR adds lacking `IF NOT EXISTS` to db indexes creation ddls in the PostgreSQL metastore init script. ## Types of changes 🔖 - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Test Plan 🧪 #### Behavior Without This Pull Request ⚰️ #### Behavior With This Pull Request 🎉 #### Related Unit Tests --- # Checklist 📝 - [x] This patch was not authored or co-authored using [Generative Tooling](https://www.apache.org/legal/generative-tooling.html) Closes #6066 from tigrulya-exe/feature/5674-postgresql-metadata-backend. Closes #6066 bb6487c16 [Tigran Manasyan] Fix PostgreSQL metastore migration script failure if indexes already exist Authored-by: Tigran Manasyan <t.manasyan@arenadata.io> Signed-off-by: Cheng Pan <chengpan@apache.org> |
||
|---|---|---|
| .. | ||
| src | ||
| web-ui | ||
| pom.xml | ||