[ https://issues.apache.org/jira/browse/CAMEL-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868914#comment-17868914 ]
Andrea Cosentino commented on CAMEL-21012: ------------------------------------------ Can you provide an example of what you're doing. The transforms are aimend to be used with langchain-embeddings component only > camel-milvus: action name mismatch with embeddings > -------------------------------------------------- > > Key: CAMEL-21012 > URL: https://issues.apache.org/jira/browse/CAMEL-21012 > Project: Camel > Issue Type: Task > Components: camel-milvus > Affects Versions: 4.7.0 > Reporter: Otavio Rodolfo Piske > Assignee: Andrea Cosentino > Priority: Major > Fix For: 4.8.0 > > > The embedding component and the Milvus component in Camel have different > behaviors when it comes to handling actions > The embedding component requires the action name to be specified as a header: > {code:xml} > <setHeader name="CamelMilvusAction"> > <constant>UPSERT</constant> > </setHeader> > {code} > However, this causes problems when using in combination with the Milvus > embedding, because the transformer creates a InsertParam object. > The problem is in the `private void upsert(Exchange exchange)` method from > MilvusProducer.java. When we try to get the body of the message, we look for > an `UpsertParam.class`. -- This message was sent by Atlassian Jira (v8.20.10#820010)