snazy opened a new issue, #767: URL: https://github.com/apache/polaris/issues/767
### Describe the bug I'm not sure whether Polaris persistence can ensure that no two entities (think: Iceberg tables & views) with the same name can ever exist. The reason I'm bringing this up is the disconnect of the name resolution vs technical ID resolution. It feels possible that two concurrent requests to e.g. create a new table pass the "that name does not yet exist" check and then both write new entities with the same name. The name checks are only _programmatic_ checks against previous read operations - but there is nothing that technically prevents having duplicate names. ### To Reproduce _No response_ ### Actual Behavior _No response_ ### Expected Behavior _No response_ ### Additional context _No response_ ### System information _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
