[GORA-132] Uses ByteBufferSerializer for column value to support various data types rather than StringSerializer

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2
• Fix Version/s: 0.2.1
• Component/s: gora-cassandra
• Assignee: Unassigned
• Reporter: Kazuomi Kashii
• Created: 15/May/12 06:21
• Updated: 26/Jul/12 15:27
• Resolved: 21/May/12 22:43

Description

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.

Issue Links

• blocks: GORA-138 gora-cassandra array type support
• is related to: GORA-138 gora-cassandra array type support
• is related to: GORA-139 Creates Cassandra column family with BytesType for column value validator (and comparators), instead of UTF8Type
• is related to: GORA-142 Creates org.apache.gora.cassandra.serializers package in order to clean the code of store and query packages and to support additional types in future.
• relates to: GORA-81 Replace CassandraStore#addOrUpdateField with TypeInferringSerializer to take advantage of when the value is already of type ByteBuffer.
• relates to: GORA-131 gora-cassandra should support other key types than String