[
https://issues.apache.org/jira/browse/OAK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-4322:
-------------------------------
Description:
Sometimes values of a property can be really huge (in an observed case a
comment was in the order of MBs). This can lead to document size going over the
limit by underlying persistence (like 16MB for mongo).
While, of course, such cases should be avoided at application level. But, from
storage side, it'd be useful to bear a bit of pain, handle the situation
gracefully (and possibly shout loudly in logs)
One possible idea is to have a configurable limit on allowed size of values. If
the size is more than that, we can potentially offload the actual value as blob
and create a proxy value (having some meta information and blob ref) in the
document.
was:
Sometimes values of a property can be really huge (in an observed case a
comment was in the order of MBs). This can lead to document size going over the
limit by underlying persistence (like 16MB for mongo).
While, of course, such cases should be avoided at application level. But, from
storage side, it'd be useful to bear a bit of pain, handle the situation
gracefully (and possibly shout loudly in logs)
> Large values of a property should be handled gracefully
> -------------------------------------------------------
>
> Key: OAK-4322
> URL: https://issues.apache.org/jira/browse/OAK-4322
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
>
> Sometimes values of a property can be really huge (in an observed case a
> comment was in the order of MBs). This can lead to document size going over
> the limit by underlying persistence (like 16MB for mongo).
> While, of course, such cases should be avoided at application level. But,
> from storage side, it'd be useful to bear a bit of pain, handle the situation
> gracefully (and possibly shout loudly in logs)
> One possible idea is to have a configurable limit on allowed size of values.
> If the size is more than that, we can potentially offload the actual value as
> blob and create a proxy value (having some meta information and blob ref) in
> the document.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)