[
https://issues.apache.org/jira/browse/GORA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040880#comment-14040880
]
Renato Javier Marroquín Mogrovejo commented on GORA-328:
--------------------------------------------------------
Hi all,
I can confirm this issue [~kminooie]. This happens when the qualifiers are
different from the field name, something like this:
{code}
<field name="name" family="p" qualifier="info:nm" ttl="11"/>
<field name="dateOfBirth" family="p" qualifier="info:db" ttl="12"/>
...
{/code}
The problem with this is was we never got the point to decide what to do with
the qualifier attribute for cassandra. I mean in gora-hbase we use it so we
don't create such a long name, but in gora-cassandra we are not forced to do
this. We should rethink this as also super column support is already dropped.
Right now all field names/column names are replaced by the qualifiers, and I
dunno if a user would easily understand this, and also we are running in the
assumption that all qualifiers are the same as the field names (of course this
is also the wrong behaviour).
Thanks a lot [~kminooie]! Let's create another issue to apply your fix there.
> Change and document default TTL value in gora-cassandra
> -------------------------------------------------------
>
> Key: GORA-328
> URL: https://issues.apache.org/jira/browse/GORA-328
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-cassandra
> Affects Versions: 0.4
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Critical
> Fix For: 0.5
>
> Attachments: GORA-328.patch
>
>
> Adding TTLs (GORA-154) is a big move forward (thanks [~renato2099]) :)
> In an scenario however where no TTL value is included, logging becomes very
> verbose and a default value of 60 is set. 60 whats?
> We can fix this easily and should also document it on the gora-cassandra
> documentation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
