[jira] [Commented] (OAK-9536) Add support in oak run for incremental indexing
[ https://issues.apache.org/jira/browse/OAK-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401523#comment-17401523 ] Nitin Gupta commented on OAK-9536: -- [https://github.com/apache/jackrabbit-oak/pull/340] > Add support in oak run for incremental indexing > --- > > Key: OAK-9536 > URL: https://issues.apache.org/jira/browse/OAK-9536 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Nitin Gupta >Assignee: Nitin Gupta >Priority: Major > > PoC level code committed on a forked repo here > [https://github.com/nit0906/jackrabbit-oak/tree/hackathon/july] . > > Need to polish this and then raise PR on Oak repository. > Also need to add documentation in the readme file for the new command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OAK-9541) ItemExistsException thrown during SysView import with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
Konrad Windszus created OAK-9541:
Summary: ItemExistsException thrown during SysView import with
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
Key: OAK-9541
URL: https://issues.apache.org/jira/browse/OAK-9541
Project: Jackrabbit Oak
Issue Type: Bug
Components: jcr
Affects Versions: 1.40.0
Reporter: Konrad Windszus
When trying to import a node via SysViewImportHandler which already exists with
a different (but non-referenced UUID) in the repo the following exception can
be observed:
{code}
javax.jcr.ItemExistsException: Node with the same UUID
exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
at
org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
~[oak-jcr-1.40.0.jar:1.40.0]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OAK-9541) ItemExistsException thrown during SysView import with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401583#comment-17401583
]
Konrad Windszus commented on OAK-9541:
--
The condition at
https://github.com/apache/jackrabbit-oak/blob/d01cb5c9dbc6ae6fdb4df58fd81ac5ed8b0536d3/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/xml/ImporterImpl.java#L423
IMHO negates the wrong expression.
Instead of
{code}
if (!(existingIdentifier.equals(id)
&& (uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
{code}
if (existingIdentifier.equals(id)
&& !(uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
> ItemExistsException thrown during SysView import with
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
> --
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists
> with a different (but non-referenced UUID) in the repo the following
> exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OAK-9541) ItemExistsException thrown during SysView import with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-9541:
-
Description:
When trying to import a node via SysViewImportHandler which already exists at
the same path with a different (but non-referenced UUID) in the repo the
following exception can be observed:
{code}
javax.jcr.ItemExistsException: Node with the same UUID
exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
at
org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
~[oak-jcr-1.40.0.jar:1.40.0]
{code}
was:
When trying to import a node via SysViewImportHandler which already exists with
a different (but non-referenced UUID) in the repo the following exception can
be observed:
{code}
javax.jcr.ItemExistsException: Node with the same UUID
exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
at
org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
~[oak-jcr-1.40.0.jar:1.40.0]
at
org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
~[oak-jcr-1.40.0.jar:1.40.0]
{code}
> ItemExistsException thrown during SysView import with
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
> --
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists at
> the same path with a different (but non-referenced UUID) in the repo the
> following exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (OAK-9541) ItemExistsException thrown during SysView import with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401583#comment-17401583
]
Konrad Windszus edited comment on OAK-9541 at 8/19/21, 10:06 AM:
-
The condition at
https://github.com/apache/jackrabbit-oak/blob/d01cb5c9dbc6ae6fdb4df58fd81ac5ed8b0536d3/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/xml/ImporterImpl.java#L423
IMHO negates the wrong expression.
Instead of
{code}
if (!(existingIdentifier.equals(id)
&& (uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
probably
{code}
if (existingIdentifier.equals(id)
&& !(uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
is meant.
was (Author: kwin):
The condition at
https://github.com/apache/jackrabbit-oak/blob/d01cb5c9dbc6ae6fdb4df58fd81ac5ed8b0536d3/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/xml/ImporterImpl.java#L423
IMHO negates the wrong expression.
Instead of
{code}
if (!(existingIdentifier.equals(id)
&& (uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
{code}
if (existingIdentifier.equals(id)
&& !(uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
> ItemExistsException thrown during SysView import with
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
> --
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists
> with a different (but non-referenced UUID) in the repo the following
> exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OAK-9541) ItemExistsException thrown during SysView import with ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401665#comment-17401665
]
Konrad Windszus commented on OAK-9541:
--
I added a failing test case in
https://github.com/apache/jackrabbit-oak/pull/343. I would appreciate some
input on this issue.
> ItemExistsException thrown during SysView import with
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
> --
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists at
> the same path with a different (but non-referenced UUID) in the repo the
> following exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OAK-9540) SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg
[ https://issues.apache.org/jira/browse/OAK-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-9540: Description: We sometimes see a SegmentNotFoundException when calling IndexDefinition.hasMatchingNodeTypeReg. This can happen after segment store GC was run, but before the index definitions are refreshed. In theory, it should never happen, as the index definitions are refreshed after compaction via LuceneIndexProviderService.registerGCMonitor. But it looks like this method is not called in all cases, or it is called too late / too early. (was: We sometimes see a SegmentNotFoundException when calling IndexDefinition.hasMatchingNodeTypeReg. This can happen after segment store GC was run, but before the index definitions are refreshed. In theory, it should never happen, as the index definitions are refreshed after compaction via LuceneIndexProviderService.registerGCMonitor. But it looks like this method is not called in all cases.) > SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg > -- > > Key: OAK-9540 > URL: https://issues.apache.org/jira/browse/OAK-9540 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing, query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > > We sometimes see a SegmentNotFoundException when calling > IndexDefinition.hasMatchingNodeTypeReg. This can happen after segment store > GC was run, but before the index definitions are refreshed. In theory, it > should never happen, as the index definitions are refreshed after compaction > via LuceneIndexProviderService.registerGCMonitor. But it looks like this > method is not called in all cases, or it is called too late / too early. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-9540) SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg
[ https://issues.apache.org/jira/browse/OAK-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401703#comment-17401703 ] Thomas Mueller commented on OAK-9540: - This PR is to auto-refresh each hour by default. For additional robustness, it also catches the SegmentNotFoundException. https://github.com/apache/jackrabbit-oak/pull/344 > SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg > -- > > Key: OAK-9540 > URL: https://issues.apache.org/jira/browse/OAK-9540 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing, query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > > We sometimes see a SegmentNotFoundException when calling > IndexDefinition.hasMatchingNodeTypeReg. This can happen after segment store > GC was run, but before the index definitions are refreshed. In theory, it > should never happen, as the index definitions are refreshed after compaction > via LuceneIndexProviderService.registerGCMonitor. But it looks like this > method is not called in all cases, or it is called too late / too early. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-9540) SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg
[ https://issues.apache.org/jira/browse/OAK-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-9540: Fix Version/s: 1.22.9 > SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg > -- > > Key: OAK-9540 > URL: https://issues.apache.org/jira/browse/OAK-9540 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing, query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.22.9 > > > We sometimes see a SegmentNotFoundException when calling > IndexDefinition.hasMatchingNodeTypeReg. This can happen after segment store > GC was run, but before the index definitions are refreshed. In theory, it > should never happen, as the index definitions are refreshed after compaction > via LuceneIndexProviderService.registerGCMonitor. But it looks like this > method is not called in all cases, or it is called too late / too early. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-9535) Support recovery of large branch merge
[
https://issues.apache.org/jira/browse/OAK-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401739#comment-17401739
]
Stefan Egli commented on OAK-9535:
--
* [PR#346|https://github.com/apache/jackrabbit-oak/pull/346] created
> Support recovery of large branch merge
> --
>
> Key: OAK-9535
> URL: https://issues.apache.org/jira/browse/OAK-9535
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
>Affects Versions: 1.40.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Major
>
> When branch changes get too large, they are committed and a journal entry is
> created as a result. This way, journal entries - in terms of their byte size
> they use up - cannot grow large.
> When a recovery happenes the mechanism is slightly different: The recovery
> attempts to store a single big journal entry. In case of MongoDB, this can
> result in the document to be larger than 16MB and below exception.
> The recovery must create multiple journal entries as well to avoid running
> into the MongoDB document size limit.
> {noformat}
> Payload document size is larger than maximum of 16777216.
> org.bson.BsonMaximumSizeExceededException: Payload document size is larger
> than maximum of 16777216.
> at
> com.mongodb.internal.connection.BsonWriterHelper.writePayload(BsonWriterHelper.java:68)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandMessage.encodeMessageBodyWithMetadata(CommandMessage.java:147)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.RequestMessage.encode(RequestMessage.java:138)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandMessage.encode(CommandMessage.java:61)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.InternalStreamConnection.sendAndReceive(InternalStreamConnection.java:248)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.UsageTrackingInternalConnection.sendAndReceive(UsageTrackingInternalConnection.java:99)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultConnectionPool$PooledConnection.sendAndReceive(DefaultConnectionPool.java:450)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.CommandProtocolImpl.execute(CommandProtocolImpl.java:72)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:226)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:269)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:131)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.executeCommand(MixedBulkWriteOperation.java:435)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.executeBulkWriteBatch(MixedBulkWriteOperation.java:261)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.access$700(MixedBulkWriteOperation.java:72)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation$1.call(MixedBulkWriteOperation.java:205)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation$1.call(MixedBulkWriteOperation.java:196)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.OperationHelper.withReleasableConnection(OperationHelper.java:501)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.execute(MixedBulkWriteOperation.java:196)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.operation.MixedBulkWriteOperation.execute(MixedBulkWriteOperation.java:71)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:211)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.executeInsertMany(MongoCollectionImpl.java:529)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.insertMany(MongoCollectionImpl.java:524)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> com.mongodb.client.internal.MongoCollectionImpl.insertMany(MongoCollectionImpl.java:518)
> [org.mongodb.mongo-java-driver:3.12.7]
> at
> org.apache.jackrabbit.oak.plugins.document.mo
[jira] [Updated] (OAK-9541) ItemExistsException: "Node with the same UUID exists" thrown during SysView import with existing different UUID
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-9541:
-
Summary: ItemExistsException: "Node with the same UUID exists" thrown
during SysView import with existing different UUID (was: ItemExistsException
thrown during SysView import with
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING)
> ItemExistsException: "Node with the same UUID exists" thrown during SysView
> import with existing different UUID
> ---
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists at
> the same path with a different (but non-referenced UUID) in the repo the
> following exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (OAK-9541) ItemExistsException: "Node with the same UUID exists" thrown during SysView import with existing different UUID
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-9541:
-
Comment: was deleted
(was: The condition at
https://github.com/apache/jackrabbit-oak/blob/d01cb5c9dbc6ae6fdb4df58fd81ac5ed8b0536d3/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/xml/ImporterImpl.java#L423
IMHO negates the wrong expression.
Instead of
{code}
if (!(existingIdentifier.equals(id)
&& (uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
probably
{code}
if (existingIdentifier.equals(id)
&& !(uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING)))
{code}
is meant. )
> ItemExistsException: "Node with the same UUID exists" thrown during SysView
> import with existing different UUID
> ---
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists at
> the same path with a different (but non-referenced UUID) in the repo the
> following exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OAK-9541) ItemExistsException: "Node with the same UUID exists" thrown during SysView import with existing different UUID
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-9541:
-
Priority: Trivial (was: Major)
> ItemExistsException: "Node with the same UUID exists" thrown during SysView
> import with existing different UUID
> ---
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Trivial
>
> When trying to import a node via SysViewImportHandler which already exists at
> the same path with a different (but non-referenced UUID) in the repo the
> following exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OAK-9541) ItemExistsException: "Node with the same UUID exists" thrown during SysView import with existing different UUID
[
https://issues.apache.org/jira/browse/OAK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401742#comment-17401742
]
Konrad Windszus commented on OAK-9541:
--
According to
https://github.com/apache/jackrabbit/blob/ed3124e5fe223dada33ce6ddf53bc666063c3f2f/jackrabbit-jcr-tests/src/main/java/org/apache/jackrabbit/test/api/SerializationTest.java#L397
and
https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#importXML(java.lang.String,%20java.io.InputStream,%20int)
the {{ItemExistsException}} is actually correct. But the message "Node with
the same UUID exists:" is definitely wrong here.
> ItemExistsException: "Node with the same UUID exists" thrown during SysView
> import with existing different UUID
> ---
>
> Key: OAK-9541
> URL: https://issues.apache.org/jira/browse/OAK-9541
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.40.0
>Reporter: Konrad Windszus
>Priority: Major
>
> When trying to import a node via SysViewImportHandler which already exists at
> the same path with a different (but non-referenced UUID) in the repo the
> following exception can be observed:
> {code}
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/tmp/referenceable/child: { jcr:primaryType = nt:unstructured}
> at
> org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.startNode(ImporterImpl.java:426)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:81)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:221)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> at
> org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)
> ~[oak-jcr-1.40.0.jar:1.40.0]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OAK-9542) Build Jackrabbit/jackrabbit-oak-trunk #321 failed
Hudson created OAK-9542: --- Summary: Build Jackrabbit/jackrabbit-oak-trunk #321 failed Key: OAK-9542 URL: https://issues.apache.org/jira/browse/OAK-9542 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #321 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #321|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/321/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/321/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-9536) Add support in oak run for incremental indexing
[ https://issues.apache.org/jira/browse/OAK-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-9536: - Fix Version/s: 1.42.0 > Add support in oak run for incremental indexing > --- > > Key: OAK-9536 > URL: https://issues.apache.org/jira/browse/OAK-9536 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Nitin Gupta >Assignee: Nitin Gupta >Priority: Major > Fix For: 1.42.0 > > > PoC level code committed on a forked repo here > [https://github.com/nit0906/jackrabbit-oak/tree/hackathon/july] . > > Need to polish this and then raise PR on Oak repository. > Also need to add documentation in the readme file for the new command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-9536) Add support in oak run for incremental indexing
[ https://issues.apache.org/jira/browse/OAK-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402016#comment-17402016 ] Nitin Gupta commented on OAK-9536: -- Merged in trunk [https://github.com/apache/jackrabbit-oak/commit/82ff9222d3a71dc3e5587c9fd79ac1b7defe677a] > Add support in oak run for incremental indexing > --- > > Key: OAK-9536 > URL: https://issues.apache.org/jira/browse/OAK-9536 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Nitin Gupta >Assignee: Nitin Gupta >Priority: Major > > PoC level code committed on a forked repo here > [https://github.com/nit0906/jackrabbit-oak/tree/hackathon/july] . > > Need to polish this and then raise PR on Oak repository. > Also need to add documentation in the readme file for the new command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OAK-9536) Add support in oak run for incremental indexing
[ https://issues.apache.org/jira/browse/OAK-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta resolved OAK-9536. -- Resolution: Fixed > Add support in oak run for incremental indexing > --- > > Key: OAK-9536 > URL: https://issues.apache.org/jira/browse/OAK-9536 > Project: Jackrabbit Oak > Issue Type: New Feature >Reporter: Nitin Gupta >Assignee: Nitin Gupta >Priority: Major > Fix For: 1.42.0 > > > PoC level code committed on a forked repo here > [https://github.com/nit0906/jackrabbit-oak/tree/hackathon/july] . > > Need to polish this and then raise PR on Oak repository. > Also need to add documentation in the readme file for the new command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
