You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (Created) (JIRA)" <ji...@apache.org> on 2012/01/16 12:00:41 UTC

[jira] [Created] (GORA-81) Replace CassandraStore#addOrUpdateField with InferringTypeSerializer to take advantage of when the value is already of type ByteBuffer.

Replace CassandraStore#addOrUpdateField with InferringTypeSerializer to take advantage of when the value is already of type ByteBuffer.
---------------------------------------------------------------------------------------------------------------------------------------

                 Key: GORA-81
                 URL: https://issues.apache.org/jira/browse/GORA-81
             Project: Gora
          Issue Type: Sub-task
            Reporter: Lewis John McGibbney


Currently CassandraStore#addOrUpdateField contains a switch statement to evaluate different types of column values but in the end the cassandraClient object ends up converting to the value to type string anyway. The InferringTypeSerializer can be used instead in order to take advantage of when the value is already of type ByteBuffer.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (GORA-81) Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.

Posted by "Lewis John McGibbney (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GORA-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212743#comment-13212743 ] 

Lewis John McGibbney commented on GORA-81:
------------------------------------------

Thread to trace this issue on hector users

http://groups.google.com/group/hector-users/browse_thread/thread/6e719120851f7c61
                
> Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GORA-81
>                 URL: https://issues.apache.org/jira/browse/GORA-81
>             Project: Apache Gora
>          Issue Type: Sub-task
>          Components: storage-cassandra
>            Reporter: Lewis John McGibbney
>             Fix For: 0.2
>
>
> Currently CassandraStore#addOrUpdateField contains a switch statement to evaluate different types of column values but in the end the cassandraClient object ends up converting to the value to type string anyway. The TypeInferringSerializer [1] can be used instead in order to take advantage of when the value is already of type ByteBuffer.
> [1] https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/serializers/TypeInferringSerializer.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (GORA-81) Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.

Posted by "Lewis John McGibbney (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GORA-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney updated GORA-81:
-------------------------------------

    Description: 
Currently CassandraStore#addOrUpdateField contains a switch statement to evaluate different types of column values but in the end the cassandraClient object ends up converting to the value to type string anyway. The TypeInferringSerializer [1] can be used instead in order to take advantage of when the value is already of type ByteBuffer.

[1] https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/serializers/TypeInferringSerializer.java

  was:Currently CassandraStore#addOrUpdateField contains a switch statement to evaluate different types of column values but in the end the cassandraClient object ends up converting to the value to type string anyway. The InferringTypeSerializer can be used instead in order to take advantage of when the value is already of type ByteBuffer.

        Summary: Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.  (was: Replace CassandraStore#addOrUpdateField with InferringTypeSerializer to take advantage of when the value is already of type ByteBuffer.)
    
> Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GORA-81
>                 URL: https://issues.apache.org/jira/browse/GORA-81
>             Project: Apache Gora
>          Issue Type: Sub-task
>          Components: storage-cassandra
>            Reporter: Lewis John McGibbney
>             Fix For: 0.2
>
>
> Currently CassandraStore#addOrUpdateField contains a switch statement to evaluate different types of column values but in the end the cassandraClient object ends up converting to the value to type string anyway. The TypeInferringSerializer [1] can be used instead in order to take advantage of when the value is already of type ByteBuffer.
> [1] https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/serializers/TypeInferringSerializer.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (GORA-81) Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.

Posted by "Lewis John McGibbney (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GORA-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney updated GORA-81:
-------------------------------------

    Fix Version/s:     (was: 0.2)
                   0.3
    
> Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GORA-81
>                 URL: https://issues.apache.org/jira/browse/GORA-81
>             Project: Apache Gora
>          Issue Type: Sub-task
>          Components: storage-cassandra
>            Reporter: Lewis John McGibbney
>             Fix For: 0.3
>
>
> Currently CassandraStore#addOrUpdateField contains a switch statement to evaluate different types of column values but in the end the cassandraClient object ends up converting to the value to type string anyway. The TypeInferringSerializer [1] can be used instead in order to take advantage of when the value is already of type ByteBuffer.
> [1] https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/serializers/TypeInferringSerializer.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira