[jira] [Comment Edited] (OAK-3141) Oak should warn when too many ordered child nodes

["Thomas Mueller (JIRA)" <ji...@apache.org>]

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

Thomas Mueller edited comment on OAK-3141 at 12/14/17 8:32 AM:
---------------------------------------------------------------

I think it would be nice if there is a good way to:

* Query support: ability to query for nodes with many child nodes (ordered / unordered). Right now I don't see a good way to query for that. With SQL, it would be something like "select * from x where (select count(\*) from child) > 10". But right now we don't support aggregate functions. And no support for subqueries.
* Warning in the log file if the 1000th, 2000th, 3000th,... child nodes is added to such a node. Configurable.

Feedback is welcome.


was (Author: tmueller):
I think it would be nice if there is a good way to:

* Query support: ability to query for nodes with many child nodes (ordered / unordered). Right now I don't see a good way to query for that. With SQL, it would be something like "select * from x where (select count(*) from child) > 10". But right now we don't support aggregate functions.
* Warning in the log file if the 1000th, 2000th, 3000th,... child nodes is added to such a node. Configurable.

Feedback is welcome.

> Oak should warn when too many ordered child nodes
> -------------------------------------------------
>
>                 Key: OAK-3141
>                 URL: https://issues.apache.org/jira/browse/OAK-3141
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0.16
>            Reporter: Jörg Hoh
>            Assignee: Thomas Mueller
>             Fix For: 1.10
>
>
> When working with the RDBMK we came into situations, that large documents did not fit into the provided db columns, there was an overflow, which caused oak not to persist the change. We fixed it by increasing the size of the column.
> But it would be nice if Oak could warn if a document exceeds a certain size (for example 2 megabytes); because this warning indicates, that on a JCR level there might be a problematic situation, for example:
> * ordered node with a large list of childnodes
> * or longstanding sessions with lots of changes, which accumulate to large documents.
> It's certainly nice to know if there's a node/document with such a problem, before the exceptions actually happens and an operation breaks.
> This message should be a warning, and should contain the JCR path of the node plus the current size. To avoid that this message is overseen, it would be good if it is written everyonce in a while (every 10 minutes?) if this condition persists.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)