You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both persistent and transient queries can cause the automatic creation of one or several new topics as part of their execution (output topic, internal topics for re-keys and changelogs). In many environments it will be the case that the user actually issuing the sql does not have topic-creation rights on the brokers, in which case some kind of "pre-flight check" tool (or other facility) would be very useful to give a list of which topic names would be created if this query were executed. Think: like the --dry-run option to many git commands. This could be either a command-line tool to do the checks for a file of sql statements or some actual SQL syntax addition.
This is even more important in the case of a broker environment where topics holding sensitive data are secured by ACLs as those ACLs will need to be manually set on the internal topics of each query to avoid accidental data leakage.
Additionally, even if the user has the ability to create topics, it is also useful to be able to track down the topics owned by a given query (could be part of explain query output in this case) in order to either ensure they were properly cleaned up or to track down the answer to questions such as "what is xxx topic on my cluster which is generating yyy traffic?".
The text was updated successfully, but these errors were encountered:
Both persistent and transient queries can cause the automatic creation of one or several new topics as part of their execution (output topic, internal topics for re-keys and changelogs). In many environments it will be the case that the user actually issuing the sql does not have topic-creation rights on the brokers, in which case some kind of "pre-flight check" tool (or other facility) would be very useful to give a list of which topic names would be created if this query were executed. Think: like the --dry-run option to many git commands. This could be either a command-line tool to do the checks for a file of sql statements or some actual SQL syntax addition.
This is even more important in the case of a broker environment where topics holding sensitive data are secured by ACLs as those ACLs will need to be manually set on the internal topics of each query to avoid accidental data leakage.
Additionally, even if the user has the ability to create topics, it is also useful to be able to track down the topics owned by a given query (could be part of
explain query
output in this case) in order to either ensure they were properly cleaned up or to track down the answer to questions such as "what is xxx topic on my cluster which is generating yyy traffic?".The text was updated successfully, but these errors were encountered: