[jira] [Assigned] (OAK-1804) TarMK compaction
[ https://issues.apache.org/jira/browse/OAK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu reassigned OAK-1804: Assignee: Alex Parvulescu > TarMK compaction > > > Key: OAK-1804 > URL: https://issues.apache.org/jira/browse/OAK-1804 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: segmentmk >Reporter: Jukka Zitting >Assignee: Alex Parvulescu > Labels: production, tools > > The TarMK would benefit from periodic "compact" operations that would > traverse and recreate (parts of) the content tree in order to optimize the > storage layout. More specifically, such compaction would: > * Optimize performance by increasing locality and reducing duplication, both > of which improve the effectiveness of caching. > * Allow the garbage collector to release more unused disk space by removing > references to segments where only a subset of content is reachable. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OAK-1804) TarMK compaction
[ https://issues.apache.org/jira/browse/OAK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-1804: - Attachment: compaction.patch Attaching initial proposal (patch against the 1.0 branch). With Jukka's help I came up with a proposal for the compaction feature. It is also exposed via the oak-run module as a standalone tool. This still has some issues with big repos because of the extended use of MemoryNodeBuilders, and still it doesn't free up all potential garbage (there are probably some corner cases I did not cover) > TarMK compaction > > > Key: OAK-1804 > URL: https://issues.apache.org/jira/browse/OAK-1804 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: segmentmk >Reporter: Jukka Zitting >Assignee: Alex Parvulescu > Labels: production, tools > Attachments: compaction.patch > > > The TarMK would benefit from periodic "compact" operations that would > traverse and recreate (parts of) the content tree in order to optimize the > storage layout. More specifically, such compaction would: > * Optimize performance by increasing locality and reducing duplication, both > of which improve the effectiveness of caching. > * Allow the garbage collector to release more unused disk space by removing > references to segments where only a subset of content is reachable. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OAK-1829) IllegalStateException while trying retrieve rows information from QueryResult
[ https://issues.apache.org/jira/browse/OAK-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007155#comment-14007155 ] David Gonzalez commented on OAK-1829: - Ran into this as well.. jcr:like(fn:lower-case(./@multiValueField), '%somevalue%’) throws IllegalStateException whereas jcr:like(./@multiValueField, '%somevalue%’) does not. > IllegalStateException while trying retrieve rows information from QueryResult > -- > > Key: OAK-1829 > URL: https://issues.apache.org/jira/browse/OAK-1829 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 0.20 >Reporter: Vijay Kumar j > > if query contain lowerCase on array property then QueryResult.getRows() > throwing IllegalStateException. > Query which causing issue > select [selector_1].* from [nt:unstructured] AS [selector_1] where > (([selector_1].[lcc:className] = > 'com.adobe.icc.dbforms.obj.ConditionalDataModule')) AND > (LOWER([selector_1].[dataDictionaryRefs]) = 'employeedd') > If we remove LOWER function then it is working > select [selector_1].* from [nt:unstructured] AS [selector_1] where > (([selector_1].[lcc:className] = > 'com.adobe.icc.dbforms.obj.ConditionalDataModule')) AND > ([selector_1].[dataDictionaryRefs] = 'EmployeeDD') -- This message was sent by Atlassian JIRA (v6.2#6252)
