gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-203) Bug in setting column field attribute "qualifier" in CassandraMapping
Date Sat, 02 Feb 2013 01:55:11 GMT

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

Lewis John McGibbney commented on GORA-203:

I think also that we could do with enforcing much more verbose logging but dropping it to
DEBUG level. What do you feel on this as well?
> 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: storage-cassandra
>    Affects Versions: 0.2.1
>            Reporter: Lewis John McGibbney
>             Fix For: 0.3
> 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

View raw message