[
https://issues.apache.org/jira/browse/OAK-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882996#comment-13882996
]
Tobias Bocanegra commented on OAK-1356:
---------------------------------------
bq. About exposing the implementation detail to the application: I wouldn't do
that.
It depends where you specify it. if the capability of a repository to have an
infinite transient space was defined by JCR (like journaled observation), this
would not be debatable. if we don't expose this descriptor, we (or users) end
up checking for files or other non-documented conditions in order to detect if
oak runs on MongoDB or not.
> Expose the preferred transient space size as repository descriptor
> -------------------------------------------------------------------
>
> Key: OAK-1356
> URL: https://issues.apache.org/jira/browse/OAK-1356
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Tobias Bocanegra
>
> The problem is that the different stores have different transient space
> characteristics. for example the MongoMK is very slow when handling large
> saves.
> suggest to expose a repository descriptor that can be used to estimate the
> preferred transient space, for example when importing content.
> so either a boolean like:
> {{option.infinite.transientspace}}
> or a number like:
> {{option.transientspace.preferred.size}}
> the later would denote the average number of modified node states that should
> be put in the transient space before the persistence starts to degrade.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
