Nicolò Boschi
Nicolò Boschi
@songjinu you're exceeding the description length of a flow. Please reduce it to be less than 1406 characters
@mehulgit could you retry with the latest version (1.0.5)?
@eolivelli since the only place you use the prompt is the completion, and you likely have only one completions agent in the application, what is the value of putting it...
The main pain point is that I want to see what is in the record at each step. the focus is on development of the pipeline. I created a pipeline...
Some examples: - language-detector uses `allowedLanguages` - unwrap-key-value uses `unwrapKey` - text-splitter uses `splitter_type`, `length_function` and others - python-* uses `className`
The plan is to write the Pulsar Heartbeat chart and import it in KAAP stack, as we did for the admin console
@pgier that problem has been resolved in Pulsar 2.8. do you still have the issue?
Thanks @MarkusNeuron I'll cut a release once CI passes and this is merged
@MarkusNeuron can you please fix the CI? I think you have to add the new values property here: https://github.com/datastax/kaap/blob/daaf6fc88d0599be04af063eb8cb1606c36558e8/tests/src/test/java/com/datastax/oss/kaap/tests/BaseK8sEnvTest.java#L215
I'm not sure why this would be a better approach. The upgrade order is mostly following the components dependencies. Also it's not obvious to understand whether the pulsar version change...