snazy opened a new issue, #2295:
URL: https://github.com/apache/polaris/issues/2295
### Describe the bug
The design of the persistence infrastructure makes the
`validateNoLocationOverlap()` prone to false results.
With the right timing, it is possible to create multiple tables with the
same base location. The flow is relatively simple and applies to tables and
views and namespaces.
```
Time Create 'A' Create 'B'
==== ---------- ----------
0 create operation starts
1 create
operation start
2 validateNoLocationOverlap("s3://foo/bar/")
--> OK (not used)
3
validateNoLocationOverlap("s3://foo/bar/")
--> OK (not
used)
4 create entity
with base location `s3://foo/bar/`
5 create entity
with base
location `s3://foo/bar/`
```
This is possible, because the `validateNoLocationOverlap()` performs 1 or
many individual calls to `PolarisMetaStoreManager`, and each of those runs in
within its own isolation (atomic or transactional). This means even
serializable isolation would not help here.
The setting of `OPTIMIZED_SIBLING_CHECK` is irrelevant here, setting it may
just make this issue harder to exploit (timing) in practice.
### 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: issues-unsubscr...@polaris.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
