[
https://issues.apache.org/jira/browse/GORA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kaveh minooie updated GORA-328:
-------------------------------
Attachment: GORA-328.patch
ok so there are couple of problems here. first, setTtl can not be used with
value 0. second in addColumn and addSubColumng instead of using the columnName,
the fieldName is being used to retrieve the ttl value from the columnAttrMap
which will not be find and that results in the default value being used all the
times. anyway this patch should fix all of those.
also I change the default value for ttl to '0', and added properties for
replication strategy and replication factor which now can be set in the mapping
file ( attributes 'rf' and 'strategy' on keyspace tag )
> 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)
