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] [Resolved] (GORA-328) Change and document default TTL value in gora-cassandra
Date Wed, 02 Jul 2014 06:25:24 GMT

     [ https://issues.apache.org/jira/browse/GORA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lewis John McGibbney resolved GORA-328.
---------------------------------------

    Resolution: Fixed

Documentation on the site updated to accommodate the great work you guys did on this one.
Thank you for your contributions this is looking great.
http://gora.apache.org/current/gora-cassandra.html

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

Mime
View raw message