Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16135
I guess the large number of lock sites is confusing me. We only want to
prevent concurrent instantiation of a single table, so shouldn't you only need
1 lock for that site?
Also, we should have a unit test that tries to concurrently read from a
table from many threads, and verifies via the catalog metrics that it is only
loaded once (see `TablePerfStatsSuite` for how to access the metrics).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
