What is the correct configuration for the RisingWave `connector` component in a Helm chart?
I'm experiencing issues with join queries in RisingWave and suspect it might be due to an incorrect configuration of the connector component in the Helm chart. Currently, only my compute pod has a connector container, and I'm not sure if it should also be scheduled in the same pod as the meta component. Can you clarify the correct setup for the connector component within the RisingWave Helm chart deployment?
Dominic Lindsay
Asked on Nov 09, 2023
Yes, the connector node should be embedded into both compute and meta processes. A Java process for the connector will be started on need, which is the more recommended way. Therefore, you can turn the connector component off in the values of the Helm chart. The recent merge request did not schedule the connector component container with the meta-component statefulset, and this should be addressed as a 'to do' in the issue.