[GitHub] [iceberg] jshmchenxi commented on pull request #2754: Core: Use current user ugi to run in WORKER_POOL to prevent wrong cre…

[GitBox <gi...@apache.org>]

jshmchenxi commented on pull request #2754:
URL: https://github.com/apache/iceberg/pull/2754#issuecomment-873335361


   > the UGI in your environment changes based on the incoming request, but the thread pool that handles planning keeps its initial user information?
   
   @rdblue Yes, that's the problem.
   I found it not elegant to add UGI related code to Iceberg, too. However, we need to use thread pool otherwise it will slow down the processing.
   
   > we could update the TableScan interface and Spark to manage thread pools at a session level.
   
   Does it mean that we should create a thread pool with a session lifetime (I'm not sure how to implement), or just replace the WORKER_POOL with a newly created one when it's necessary?


-- 
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-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org