Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce the concept of a namespace #3966

Closed
big-andy-coates opened this issue Nov 23, 2019 · 1 comment
Closed

Introduce the concept of a namespace #3966

big-andy-coates opened this issue Nov 23, 2019 · 1 comment
Milestone

Comments

@big-andy-coates
Copy link
Contributor

With reference to the PR that introduced TERMINATE ALL syntax.

We might look to introduce the concept of a namespace, (and a catalogue to track them), to which entities such as streams, tables, types, can be added.

We should support dropping a namespace as a unit. This will go some way to addressing issues like:

In the future, we may want to allow ACLs to be applied at the namespace level to allow/deny users access to them.

@big-andy-coates
Copy link
Contributor Author

Closing as, while we may choose to add the concept of namespaces in the future, they are not needed to fix the issues with TERMINATE.

Instead, I'll be raising a KLIP proposing we drop INSERT INTO in favour of a SQL UNION, meaning all persistent queries are 1-2-1 with a data source. Then we make it so that dropping the source drops the persistent query, and then we can remove TERMINATE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant