[
https://issues.apache.org/jira/browse/GORA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279765#comment-13279765
]
Lewis John McGibbney commented on GORA-132:
-------------------------------------------
I've run this patch against some tests with Nutchgora branch and the tutorial
and I'm happy to commit unless there are other objections. W.r.t the actual
issue, it addresses GORA-81, which originally came about through discussion
with some of the guys over at hector-dev@. Also it addresses the TODO in
CassandraClient.
Generally speaking, I wonder if you can comment on what kind of performance
improvements we can expect with ByteBuffer rather than String?
Thank you
> Uses ByteBufferSerializer for column value to support various data types
> rather than StringSerializer
> -----------------------------------------------------------------------------------------------------
>
> Key: GORA-132
> URL: https://issues.apache.org/jira/browse/GORA-132
> Project: Apache Gora
> Issue Type: Improvement
> Components: storage-cassandra
> Affects Versions: 0.2
> Reporter: Kazuomi Kashii
> Fix For: 0.3
>
> Attachments: GORA-131-132-v2.patch, GORA-131-132-v2.patch,
> GORA-131-132.patch
>
>
> When I made a patch to GORA-131, I noticed that gora-cassandra uses
> StringSerializer for column value.
> However, since it needs to support various value types, I think ByteBuffer is
> better than String to/from Hector,
> and gora-cassandra layer should convert values between Gora data bean value
> type and 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
