You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2021/07/29 16:27:54 UTC

[GitHub] [pinot] apucher opened a new issue #7227: Should /tables return only tables with READ permissions to the current user?

apucher opened a new issue #7227:
URL: https://github.com/apache/pinot/issues/7227


   `/tables` isn't currently bound to table-specific permissions.
   
   Intuitively, it makes sense to only show tables that actually have READ permissions to the current user - as in both metadata and data. However there are two counterpoints as well: (1) it's conceivable that there could be metadata "bot" user that can create, update, and delete tables without being able to read the metadata, and (2) the control over data-access is actually with the broker's auth and configured independently of the controller's metadata ACLs


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

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



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