Extend the CassandraPersistenceManager API with functions supported by the
Hector API
-------------------------------------------------------------------------------------
Key: AMDATU-363
URL: http://jira.amdatu.org/jira/browse/AMDATU-363
Project: Amdatu
Issue Type: New Feature
Components: Amdatu Cassandra
Reporter: Ivo Ladage - van Doorn
The CassandraPersistenceManager API sits on top of the Hector API but provides
a simplified interface. Sometimes this is handy, but for some use cases the
Hector API provides features that are needed. The question is if it useful to
wrap the Hector API in a new API, or that we should just expose the Hector API.
I think there are 3 options:
- Extend the CassandraPersistenceManager API with missing features (so that it
becomes a Hector API look-a-like)
- Publish the Hector API next to the CassandraPersistenceManager API so that a
developer can choose which one to use
- Remove the CassandraPersistenceManager API and publish the Hector API, which
will become the only Cassandra API
Features that the current CassandraPersistenceManager API offers on top of the
Hector API:
- multi-tenancy
- PersistenceManager as a service
- new functions like exists(String columnFamilyName, String rowKey) and
getRowKeys(String columnFamilyName)
- reduce/hide complexity of the Hector API (i.e. dealing with tombstone rows)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
