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

Views' creation automation #187

Open
bart182 opened this issue Sep 18, 2019 · 4 comments
Open

Views' creation automation #187

bart182 opened this issue Sep 18, 2019 · 4 comments

Comments

@bart182
Copy link

bart182 commented Sep 18, 2019

Due to the nature of our projects - developers quite often are creating new topics. Our infrastructure is growing so pretty often there is a need to add new clusters to Kafka Webview and later on create new views for each topic on cluster. Is there any possibility to create views from such topics automatically instead creating view manually for each topic?

Same story with filters - In order to improve visibility for each view we do have some filters applied. Is there a possibility to apply filters "in bulk action" instead applying filters manually on each view separately?

@Crim
Copy link
Collaborator

Crim commented Sep 18, 2019

Applying filters in bulk seems simple enough to add in, or even being able to set a filter to be included on new views by default.

For auto-creating views, I'd like to get a better understanding of how would you expect it to work?

I have a couple potential ideas:

  • Would new topics get a view that just defaults to using string deserializers?
  • Would you define a 'template view' with deserializers and filters set, and that would get applied to all new topics it discovers?
  • Would it be better to set a default key & message deserializer, and then be able to browse topics w/o having to create a view using those values? Potentially w/ the option to swap out the deserializers on the fly

Or some other ideas?

Thanks!

@bart182
Copy link
Author

bart182 commented Sep 19, 2019

Thanks for prompt response Crim,
This needs to be as easy as possible to use by developers with clear and quick feedback on what is going on topics so option2 that you mentioned would be a good solution: views with proper filters would be automatically created and for ops this would save a lot of time with maintenance on topics, their views, deserializers and filters

@Crim
Copy link
Collaborator

Crim commented Sep 19, 2019

Thanks for the feedback. I'll give it some thought about the best way to implement something like this.

I definitely like the idea of being able to browse topics in a more adhoc way, and a modifiable default template seems like the best approach so far.

There's a chance I won't be able to dive into this until mid October.

@bart182
Copy link
Author

bart182 commented Oct 21, 2019

Thanks Crim, please let me know whenever new solution/feature will be implemented

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

No branches or pull requests

2 participants