You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gora.apache.org by "Renato Javier Marroquín Mogrovejo (JIRA)" <ji...@apache.org> on 2013/02/10 19:35:13 UTC

[jira] [Commented] (GORA-205) Dedup CassandraMapping and CassandraMappingManager

    [ https://issues.apache.org/jira/browse/GORA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575483#comment-13575483 ] 

Renato Javier Marroquín Mogrovejo commented on GORA-205:
--------------------------------------------------------

I think what we have to do is to make CassandraMappingManager responsible to handle CassandraMapping. A good example on how to do this is the way it is done within the Gora-HBase module.
                
> Dedup CassandraMapping and CassandraMappingManager
> --------------------------------------------------
>
>                 Key: GORA-205
>                 URL: https://issues.apache.org/jira/browse/GORA-205
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: storage-cassandra
>    Affects Versions: 0.2.1
>            Reporter: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 0.4
>
>
> We have a pile of what looks lie deduplication between these two classes.
> We should make a determination of what is required and then document it within the appropriate class.
> This will enable easy navigation of keyspace definition etc. from within gora-cassandra. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira