[jira] [Commented] (OAK-9510) Build Jackrabbit/jackrabbit-oak-trunk #295 failed
[ https://issues.apache.org/jira/browse/OAK-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388692#comment-17388692 ] Hudson commented on OAK-9510: - Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #302|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/302/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/302/console] > Build Jackrabbit/jackrabbit-oak-trunk #295 failed > - > > Key: OAK-9510 > URL: https://issues.apache.org/jira/browse/OAK-9510 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #295 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #295|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/295/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/295/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-9510) Build Jackrabbit/jackrabbit-oak-trunk #295 failed
[ https://issues.apache.org/jira/browse/OAK-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388542#comment-17388542 ] Hudson commented on OAK-9510: - Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #301|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/301/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/301/console] > Build Jackrabbit/jackrabbit-oak-trunk #295 failed > - > > Key: OAK-9510 > URL: https://issues.apache.org/jira/browse/OAK-9510 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #295 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #295|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/295/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/295/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-8048) VersionHistory not removed when removing node and all its versions
[
https://issues.apache.org/jira/browse/OAK-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388525#comment-17388525
]
Marco Piovesana commented on OAK-8048:
--
Hi guys, it this on hold or do you already have an idea of when it will be
fixed?
thanks, Marco.
> VersionHistory not removed when removing node and all its versions
> --
>
> Key: OAK-8048
> URL: https://issues.apache.org/jira/browse/OAK-8048
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Affects Versions: 1.8.9
>Reporter: Marco Piovesana
>Assignee: Manfred Baedke
>Priority: Major
> Attachments: OAK-8048-test.diff, OAK-8048.diff, fix-OAK-8048.patch
>
>
> Hi all,
> I'm trying to delete a node and all its versions, but the version history is
> not removed. I'm doing the following steps (as described in OAK-4370 and
> JCR-134):
> # retrieve the version history
> # delete the node and save the session
> # delete all versions except for the base version
> # save the session
> The versions are all gone but the versionHistory node, and the base version
> node, are still there. Am I doing something wrong?
> The only test related to this that I found is
> {{ReadOnlyVersionManagerTest.testRemoveEmptyHistoryAfterRemovingVersionable}}.
> It does work, but uses Oak related classes and not the JCR interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OAK-9434) MongoDB indexing: implement parallel chunk download
[ https://issues.apache.org/jira/browse/OAK-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388524#comment-17388524 ] Amrit Verma commented on OAK-9434: -- Configurations added - *Sort strategy type* - [https://github.com/apache/jackrabbit-oak/blob/1621b9d56434ee4a6f2cd19863f94d963d68ac91/oak-run-commons/src/main/java/org/apache/jackrabbit/oak/index/indexer/document/flatfile/FlatFileNodeStoreBuilder.java#L53]. | Example test - [https://github.com/apache/jackrabbit-oak/blob/1621b9d56434ee4a6f2cd19863f94d963d68ac91/oak-run-commons/src/test/java/org/apache/jackrabbit/oak/index/indexer/document/flatfile/FlatFileStoreTest.java#L102] *Thread pool size for parallel download* - [https://github.com/apache/jackrabbit-oak/blob/1621b9d56434ee4a6f2cd19863f94d963d68ac91/oak-run-commons/src/main/java/org/apache/jackrabbit/oak/index/indexer/document/flatfile/MultithreadedTraverseWithSortStrategy.java#L326] *Existing data dump dir (to resume from where previous download stopped)* - [https://github.com/apache/jackrabbit-oak/blob/1621b9d56434ee4a6f2cd19863f94d963d68ac91/oak-run-commons/src/main/java/org/apache/jackrabbit/oak/index/IndexOptions.java#L106-L108] - This option, if specified, should point to the flat file store directory in the indexing work dir - See example test case - [https://github.com/apache/jackrabbit-oak/blob/1621b9d56434ee4a6f2cd19863f94d963d68ac91/oak-run-commons/src/test/java/org/apache/jackrabbit/oak/index/indexer/document/flatfile/FlatFileStoreTest.java#L175] > MongoDB indexing: implement parallel chunk download > --- > > Key: OAK-9434 > URL: https://issues.apache.org/jira/browse/OAK-9434 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Affects Versions: 1.38.0 >Reporter: Amrit Verma >Assignee: Amrit Verma >Priority: Major > > In case of large indexes, indexing takes a long time. In case of MongoDB > Document store, Currently it is a two step process - download the data from > mongodb then create index based on that data. > If something fails during this process, indexing needs to be restarted from > beginning of the download step. We should make the indexing process resumable > from the point it stopped. > Since data download from mongodb seems to be more time taking than indexing > itself, we first focus on download part. > This Jira issue is for implementing resumable/parallel download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OAK-9434) MongoDB indexing: implement parallel chunk download
[ https://issues.apache.org/jira/browse/OAK-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amrit Verma resolved OAK-9434. -- Resolution: Fixed > MongoDB indexing: implement parallel chunk download > --- > > Key: OAK-9434 > URL: https://issues.apache.org/jira/browse/OAK-9434 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Affects Versions: 1.38.0 >Reporter: Amrit Verma >Assignee: Amrit Verma >Priority: Major > > In case of large indexes, indexing takes a long time. In case of MongoDB > Document store, Currently it is a two step process - download the data from > mongodb then create index based on that data. > If something fails during this process, indexing needs to be restarted from > beginning of the download step. We should make the indexing process resumable > from the point it stopped. > Since data download from mongodb seems to be more time taking than indexing > itself, we first focus on download part. > This Jira issue is for implementing resumable/parallel download. -- This message was sent by Atlassian Jira (v8.3.4#803005)
