[
https://issues.apache.org/jira/browse/GORA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696508#comment-13696508
]
Hudson commented on GORA-203:
-----------------------------
Integrated in goraOracle #6 (See [https://builds.apache.org/job/goraOracle/6/])
GORA-203 Bug in setting column field attribute qualifier in
CassandraMapping (Revision e7bb428cfa979ad49f355f8bc85ba98b50eb34f3)
Result = FAILURE
lewismc :
Files :
* CHANGES.txt
*
gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraMapping.java
*
gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraMappingManager.java
> Bug in setting column field attribute "qualifier" in CassandraMapping
> ----------------------------------------------------------------------
>
> Key: GORA-203
> URL: https://issues.apache.org/jira/browse/GORA-203
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-cassandra
> Affects Versions: 0.2.1
> Reporter: Lewis John McGibbney
> Fix For: 0.3
>
> Attachments: GORA-203.patch, GORA-203-v2.patch
>
>
> Currently, we are absolutely required to set a value for a column field
> attribute "qualifier", however there are no checks to determine whether this
> is actually present or not, therefore this is a bug.
> Renato pointed this out and hopefully he can upload some stack traces
> relating to the issue to display the kind of issues one faces when qualifier
> attributes and their values are not present when mapping columns to Cassandra.
> As far as we know, column field attributes are supported in the most recent
> Cassandra data model (and this is not due to change) therefore we should also
> support them in Gora, however it is my opinion (please comment here) on
> whether they should be optional or not.
--
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
