Replies: 6 comments 3 replies
-
Hi Christian, thanks for reporting this. @maltesander had a quick look earlier and this looks like a bug on our side. It looks like we override extensions :( Thanks and have a great weekend! |
Beta Was this translation helpful? Give feedback.
-
Hi, Is there any way we can still override the loadList ? (With another method than the configOverrides) Thanks |
Beta Was this translation helpful? Give feedback.
-
I'm afraid with "normal" methods there is no way to do this. You'll need to scale the druid operator deployment to 0 replicas, so the operator doesn't revert your manual changes immediately. Then edit the broker configmap and restart the broker sts. Not pretty but depending on your needs might get it done for now. |
Beta Was this translation helpful? Give feedback.
-
Hi, ok I see :) Are there any future plans to add this possibility to load more extensions ? :) Have a great day, |
Beta Was this translation helpful? Give feedback.
-
Absolutely! We'll also definitely look at the overrides, as that should work. There are just too many settings in these components for us to expose all of them at once, we are constantly evaluating which ones make sense to expose directly though, and direct feedback like in this case from you always goes to the top of the list! |
Beta Was this translation helpful? Give feedback.
-
There is also stackabletech/druid-operator#416 which will make this easier once discussed and merged. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I hope you may help me. I've tried now every possibility to use the "configOvverrides" to load additionnel extensions, but they are not reflected in the configmap.
Is this not implemented by the operator or am I using this the wrong way? :)
Thank you for your advice,
Christian
Beta Was this translation helpful? Give feedback.
All reactions