Github user fhussonnois commented on the pull request:
https://github.com/apache/storm/pull/827#issuecomment-158930102
@satishd I think the fluent API handles common use cases. Its purpose is to
ease the cassandra integration because creating a CQL statement from tuple is
cumbersome. In case of specifics needs developers can still implement their own
CQLStatementTupleMapper. So I think it will be bad to remove that API. In fact,
there is a risk that developers that will use the connector have to re-develop
a DSL.
I'm not sure, but I think there is not a lot changes into cassandra
connector API. DataStax seems to focus their developments onto the cassandra
internal system and not onto query language support.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
