jon-wei edited a comment on issue #9380: URL: https://github.com/apache/druid/issues/9380#issuecomment-657952384
@pjain1 I had a few specific comments on the spreadsheet items: - For treating Lookups as Datasources, I could see one day that these concepts have less distinction, but I think we currently allow for lookups and datasources to share the same name, so I think they'd need to be separate resources for now - The GET for `GET /druid/coordinator/v1/config/compaction` is filtered based on READ DATASOURCE permissions, but I think we may want to somehow represent that differently. The compaction stuff is more of a write/datasource management thing, and I think a read-datasource-only user shouldn't necessarily have access to compaction configs. - Similarly, I think system schema tasks/supervisors and coordinator load rule GETs shouldn't be represented as READ DATASOURCE. - For LOOKUP INTERNAL type resources, could that just be INTERNAL/INTERNAL? I also have a more general question: What would the migration process to a version with the new resource definitions look like for users? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
