You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2014/03/03 15:11:20 UTC

[jira] [Commented] (OAK-1481) clarify DS.find caching behavior

    [ https://issues.apache.org/jira/browse/OAK-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918073#comment-13918073 ] 

Julian Reschke commented on OAK-1481:
-------------------------------------

...vielleicht noch "in ms" hinzufügen...?


> clarify DS.find caching behavior
> --------------------------------
>
>                 Key: OAK-1481
>                 URL: https://issues.apache.org/jira/browse/OAK-1481
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core
>            Reporter: Julian Reschke
>            Assignee: Marcel Reutegger
>            Priority: Trivial
>             Fix For: 0.18
>
>
> The Javadoc for "find(Collection<T> collection, String key, int maxCacheAge)" should be clarified wrt:
> - maxCacheAge == 0 (mongods seems to invalidate)
> and for "<T extends Document> T find(Collection<T> collection, String key)"
> - what the implied caching behavior is (mongods seems to assume Integer.MAX_VALUE)



--
This message was sent by Atlassian JIRA
(v6.2#6252)