gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-138) gora-cassandra array type support
Date Fri, 01 Jun 2012 14:35:23 GMT

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

Hudson commented on GORA-138:
-----------------------------

Integrated in gora-trunk #300 (See [https://builds.apache.org/job/gora-trunk/300/])
    commit to address GORA-138 & 81 and update to CHANGES.txt (Revision 1345164)

     Result = SUCCESS
lewismc : 
Files : 
* /gora/trunk/CHANGES.txt
* /gora/trunk/gora-cassandra/src/main/java/org/apache/gora/cassandra/query/CassandraColumn.java
* /gora/trunk/gora-cassandra/src/main/java/org/apache/gora/cassandra/query/CassandraResult.java
* /gora/trunk/gora-cassandra/src/main/java/org/apache/gora/cassandra/query/CassandraSubColumn.java
* /gora/trunk/gora-cassandra/src/main/java/org/apache/gora/cassandra/query/CassandraSuperColumn.java
* /gora/trunk/gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraClient.java
* /gora/trunk/gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraStore.java

                
> gora-cassandra array type support 
> ----------------------------------
>
>                 Key: GORA-138
>                 URL: https://issues.apache.org/jira/browse/GORA-138
>             Project: Apache Gora
>          Issue Type: New Feature
>          Components: storage-cassandra
>    Affects Versions: 0.2
>            Reporter: Kazuomi Kashii
>             Fix For: 0.3
>
>         Attachments: GORA-131-132-133-134.patch, GORA-138-v2.patch, GORA-138.patch
>
>
> In order to support ARRAY in gora-cassandra, we have two scenarios as follows:
> 1) super column family like the current MAP implementation; or
> 2) single column to store all elements of ARRAY.
> Each senario has pros and cons, but I'd prefer 1) and I have implemented a prototype.
> 1) super column family
> ** pros
> - consistent with MAP
> - each column stores primitive type value.
> ** cons
> - ARRAY cannot be contained in RECORD or MAP.
> 2) single column
> ** pros
> - complex type such as RECORD and MAP can have ARRAY value.
> ** cons
> - large size of ARRAY requres a huge single column value.
> - difficult to implement for STRING and BYTES (variable length).
> Currently, super column is used for other complex types such as RECORD and MAP,
> so it is consistent to use super column for ARRAY.
> Considering this, the rule that complex type cannot have complex type value
> seems a reasonable limitation, and it makes rule simple.
> If we take 1) senario with super column family,
> I can provide a patch of my implementation.

--
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

        

Mime
View raw message