JeonDaehong commented on issue #8729: URL: https://github.com/apache/gravitino/issues/8729#issuecomment-3596319350
> @JeonDaehong > Would you like to move on this issue? I think we can summarize it this way 1. It makes sense to reset lockType to null after all locks are released. 2. Since the current design assumes single-threaded usage, enforcing thread ownership for unlock() is reasonable. 3. And the memory-visibility concern doesn’t seem critical under the current lifecycle and usage pattern. Given that the issue is somewhat ambiguous, I haven’t opened a PR for it yet. Let me know if this understanding aligns with your expectations. -- 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]
