[GitHub] [druid] abhishekagarwal87 commented on pull request #13766: Operator conversion deny list

["abhishekagarwal87 (via GitHub)" <gi...@apache.org>]

abhishekagarwal87 commented on PR #13766:
URL: https://github.com/apache/druid/pull/13766#issuecomment-1425265622

   if it's for security concerns, can we tie this to role-based access control? Like how we did for query context params. Also, would you want to disable access to an operator or would you like to disable access to an underlying resource that the said operator accesses? So if you're going to disallow access to external resources, wouldn't it be better for an admin to remove "External read" permission, no matter which operator needs that access? 


-- 
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: commits-unsubscribe@druid.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org