[jira] [Created] (OAK-10213) Add new api in DocumentStore to handle bulk findAndUpdate operations
Rishabh Daim created OAK-10213: -- Summary: Add new api in DocumentStore to handle bulk findAndUpdate operations Key: OAK-10213 URL: https://issues.apache.org/jira/browse/OAK-10213 Project: Jackrabbit Oak Issue Type: Improvement Reporter: Rishabh Daim Assignee: Rishabh Daim Currently, we only provide support to update 1 document using [findAndUpdate|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentStore.java#L348] with conditions. For my ticket OAK-10199, I need to update multiple documents. However, none of the existing APIs fit my use case. Using [findAndUpdate|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentStore.java#L348] would be very inefficient in case of updating multiple documents. Hence I propose adding a new API that can update multiple documents using [bulkUpdate|https://www.mongodb.com/docs/drivers/java/sync/current/usage-examples/bulkWrite/] of Mongo on similar lines to the [createOrUpdate|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentStore.java#L321] API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10212) Binary references file in the newly created archive might be missing
[ https://issues.apache.org/jira/browse/OAK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miroslav Smiljanic updated OAK-10212: - Description: [TarWriter.flush |https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.50.0/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/file/tar/TarWriter.java#L177-L193] first saves segments and then binary references file. Because of that, in a newly created archive for the remote segment store, binary references file might be missing. Because of that, the operation of collection binary references will fail, for example, during datastore garbage collection. > Binary references file in the newly created archive might be missing > > > Key: OAK-10212 > URL: https://issues.apache.org/jira/browse/OAK-10212 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-azure >Affects Versions: 1.50.0 >Reporter: Miroslav Smiljanic >Assignee: Miroslav Smiljanic >Priority: Major > > [TarWriter.flush > |https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.50.0/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/file/tar/TarWriter.java#L177-L193] > first saves segments and then binary references file. > Because of that, in a newly created archive for the remote segment store, > binary references file might be missing. Because of that, the operation of > collection binary references will fail, for example, during datastore garbage > collection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10212) Binary references file in the newly created archive might be missing
Miroslav Smiljanic created OAK-10212: Summary: Binary references file in the newly created archive might be missing Key: OAK-10212 URL: https://issues.apache.org/jira/browse/OAK-10212 Project: Jackrabbit Oak Issue Type: Improvement Components: segment-azure Affects Versions: 1.50.0 Reporter: Miroslav Smiljanic Assignee: Miroslav Smiljanic -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10210) Prefetch breaks Fast Result Size
[ https://issues.apache.org/jira/browse/OAK-10210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-10210. -- Fix Version/s: 1.52.0 Resolution: Fixed Merged on 2023-04-26 > Prefetch breaks Fast Result Size > > > Key: OAK-10210 > URL: https://issues.apache.org/jira/browse/OAK-10210 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Thomas Mueller >Priority: Major > Labels: query > Fix For: 1.52.0 > > > If prefetch is enabled, then fast result size won't work. > The problem is that PrefetchCursor (in oak-core) doesn't implement getSize as > it should. It is easy to fix, but we didn't know this so far. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10211) Rectify documentation for hybrid indexes
[
https://issues.apache.org/jira/browse/OAK-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohit Kataria updated OAK-10211:
Description:
The documentation for "synchronous Lucene property indexes"(hybrid indexes) is
linked to
[https://jackrabbit.apache.org/archive/wiki/JCR/Synchronous-Lucene-Property-Indexes_115513516.html]
But the info is not correct, the document suggests following index definition:
{code:java}
/oak:index/assetType
- jcr:primaryType = "oak:QueryIndexDefinition"
- type = "lucene"
- async = ["async", "sync"]
+ indexRules
+ nt:base
+ properties
+ resourceType
- propertyIndex = true
- name = "assetType"
- sync = true {code}
But it should be
{code:java}
async = ["async", "nrt"] {code}
h4.
was:
The documentation for "synchronous Lucene property indexes" is linked to
[https://jackrabbit.apache.org/archive/wiki/JCR/Synchronous-Lucene-Property-Indexes_115513516.html]
But the info is not correct, the document suggests following index definition:
{code:java}
/oak:index/assetType
- jcr:primaryType = "oak:QueryIndexDefinition"
- type = "lucene"
- async = ["async", "sync"]
+ indexRules
+ nt:base
+ properties
+ resourceType
- propertyIndex = true
- name = "assetType"
- sync = true {code}
But it should be
{code:java}
async = ["async", "nrt"] {code}
h4.
> Rectify documentation for hybrid indexes
>
>
> Key: OAK-10211
> URL: https://issues.apache.org/jira/browse/OAK-10211
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Mohit Kataria
>Assignee: Mohit Kataria
>Priority: Minor
>
> The documentation for "synchronous Lucene property indexes"(hybrid indexes)
> is linked to
> [https://jackrabbit.apache.org/archive/wiki/JCR/Synchronous-Lucene-Property-Indexes_115513516.html]
>
> But the info is not correct, the document suggests following index
> definition:
> {code:java}
> /oak:index/assetType
> - jcr:primaryType = "oak:QueryIndexDefinition"
> - type = "lucene"
> - async = ["async", "sync"]
> + indexRules
> + nt:base
> + properties
> + resourceType
> - propertyIndex = true
> - name = "assetType"
> - sync = true {code}
> But it should be
> {code:java}
> async = ["async", "nrt"] {code}
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-10211) Rectify documentation for hybrid indexes
[
https://issues.apache.org/jira/browse/OAK-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohit Kataria updated OAK-10211:
Summary: Rectify documentation for hybrid indexes (was: Rectify
Documentation for synchronous Lucene property indexes)
> Rectify documentation for hybrid indexes
>
>
> Key: OAK-10211
> URL: https://issues.apache.org/jira/browse/OAK-10211
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Mohit Kataria
>Assignee: Mohit Kataria
>Priority: Minor
>
> The documentation for "synchronous Lucene property indexes" is linked to
> [https://jackrabbit.apache.org/archive/wiki/JCR/Synchronous-Lucene-Property-Indexes_115513516.html]
>
> But the info is not correct, the document suggests following index
> definition:
> {code:java}
> /oak:index/assetType
> - jcr:primaryType = "oak:QueryIndexDefinition"
> - type = "lucene"
> - async = ["async", "sync"]
> + indexRules
> + nt:base
> + properties
> + resourceType
> - propertyIndex = true
> - name = "assetType"
> - sync = true {code}
> But it should be
> {code:java}
> async = ["async", "nrt"] {code}
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10211) Rectify Documentation for synchronous Lucene property indexes
Mohit Kataria created OAK-10211:
---
Summary: Rectify Documentation for synchronous Lucene property
indexes
Key: OAK-10211
URL: https://issues.apache.org/jira/browse/OAK-10211
Project: Jackrabbit Oak
Issue Type: Improvement
Components: indexing
Reporter: Mohit Kataria
Assignee: Mohit Kataria
The documentation for "synchronous Lucene property indexes" is linked to
[https://jackrabbit.apache.org/archive/wiki/JCR/Synchronous-Lucene-Property-Indexes_115513516.html]
But the info is not correct, the document suggests following index definition:
{code:java}
/oak:index/assetType
- jcr:primaryType = "oak:QueryIndexDefinition"
- type = "lucene"
- async = ["async", "sync"]
+ indexRules
+ nt:base
+ properties
+ resourceType
- propertyIndex = true
- name = "assetType"
- sync = true {code}
But it should be
{code:java}
async = ["async", "nrt"] {code}
h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
