[gatein-issues] [JBoss JIRA] (GTNPORTAL-3518) Use a variable to enable the sequence

[Peter Palaga (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga resolved GTNPORTAL-3518.
-------------------------------------

    Resolution: Done


> Use a variable to enable the sequence
> -------------------------------------
>
>                 Key: GTNPORTAL-3518
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3518
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: JCR integration
>    Affects Versions: 3.8.2.Final
>            Reporter: Nicolas Filotto
>             Fix For: 3.8.5.Final, 3.9.0.Final
>
>
> Starting from eXo JCR 1.16.0 Alpha4, we have an improvement (aka https://jira.exoplatform.org/browse/JCR-2262) that allows to provide a better scalability in term of total amount of sub nodes that a node can have without affecting the performances, indeed with big tables the performances get worse especially when we have a node with a lot of sub nodes so to push the scalability limit, eXo JCR can now rely on sequences. 
> The sequences can be enabled thanks to a new parameter in the data container configuration of the workspace called {{use-sequence-for-order-number}}, by default it is set to {{auto}} so it will be enabled on all the databases on which we know that the sequences help to improve the performances and the scalability such as on Oracle and PostgreSQL, but also on H2 and HSQLDB.
> Unfortunately, this improvement causes a regression which is (https://jira.exoplatform.org/browse/JCR-2322), so as workaround we can configure this parameter using a variable with {{false}} as default value, this way once the bug will be fixed, we will be able to set it back to the default value which is {{auto}}.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)