Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We've been stuck attempting to upgrade our existing ESB routes from v7 to v8 and have been hitting a wall, the main issue at the moment appears to be that Talend no longer supports any Camel Cassandra CQL features in v8.
This has left us wondering if Talend is even a rational choice of product to continue to use.
If anyone is successfully using Cassandra (with the Datastax mapper) from ESB routes we'd love to see how:
Hi
The "camel-cassandraql" karaf feature was removed in Camel 3.x (https://issues.apache.org/jira/browse/CAMEL-16422)
It was available in Camel 2.x for Talend 7.3.1. but in Talend 8.0.1 its not available anymore.
That means you will not able to build cMessagingEndpoint + cassandraql Route as OSGi type and deploy it into Runtime.
Building this kind of Route as Microservice may still working as alternative solution.
Regards
Shong
Thanks Shong, this is what support told us as well, but it doesn't appear to be entirely true.
Because, if everyone is talking about this "camel-cassandraql" component (https://mvnrepository.com/artifact/org.apache.camel/camel-cassandraql) It appears to be alive and well in Camel 3 and 4.
And if I'm reading your answer correctly, it would still be fair to say that Talend v8 does not support this, perhaps with the fineprint of under the "default" (ESB cluster) runtime.
If it helps, we are not using cMessagingEndpoints, these are mainly cProcessors and cConfigs, due to the aforementioned DataMappers
Hi @altai otgonyin
After discussion with our developers, we decide to add back Camel-Cassandraql Karaf feature, it's fixed now. see
https://issues.apache.org/jira/browse/CAMEL-19984
Regards
Shong