sundapeng commented on PR #10350:
URL: https://github.com/apache/paimon/pull/10350#issuecomment-6555480028

   @JingsongLi the finding from the 10-26 review is addressed in `84363ffb61` 
and the thread answered: the cached FileIO of a REST token is scoped to an 
immutable copy of the catalog options it was built from, so two instances 
sharing one vended token with different catalog-only origin/target endpoints 
each select their own.
   
   I audited the other endpoint-bound caches against the same class: Jindo's 
static filesystem cache is keyed by the full Hadoop options, the 
HadoopCompliantFileIO/ResolvingFileIO/UriReaderFactory caches are per instance, 
the token stays per RESTTokenFileIO, and Lance/Vortex take the origin's 
`hadoopOptions` of the effective configuration. The Python side is fixed in 
#10351 (`52fb0b9c86`), and the Rust client needed no change.
   
   `39e3428fa2` is the current head, with the io-cache view types kept in one 
internal interface; CI is green there. Could you take another look when you 
have time?


-- 
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]

Reply via email to