[jira] [Created] (OAK-10457) Add support to filter and sort a given FFS based provided with predicates and preffered paths
Nitin Gupta created OAK-10457: - Summary: Add support to filter and sort a given FFS based provided with predicates and preffered paths Key: OAK-10457 URL: https://issues.apache.org/jira/browse/OAK-10457 Project: Jackrabbit Oak Issue Type: Task Reporter: Nitin Gupta Given a base FFS on root / , which is only sorted by path without considering preferredPathElements, and a set of preferredPathElements and a predicate based on include/exclude paths, produce a new FFS that is filtered and sorted based on the provided predicate and preferred path. Also write a test to verify an FFS produced this was is exactly similar to one produced by normal FFS creation process that picks the preferredPathElements and predicates from the index definition. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10456) oak-search-elastic: log index name when bulk update fails
[ https://issues.apache.org/jira/browse/OAK-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino updated OAK-10456: --- Summary: oak-search-elastic: log index name when bulk update fails (was: oak-search-elastic: long index name when bulk update fails) > oak-search-elastic: log index name when bulk update fails > - > > Key: OAK-10456 > URL: https://issues.apache.org/jira/browse/OAK-10456 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10456) oak-search-elastic: long index name when bulk update fails
Fabrizio Fortino created OAK-10456: -- Summary: oak-search-elastic: long index name when bulk update fails Key: OAK-10456 URL: https://issues.apache.org/jira/browse/OAK-10456 Project: Jackrabbit Oak Issue Type: Improvement Components: indexing Reporter: Fabrizio Fortino Assignee: Fabrizio Fortino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10455) synchronous commit
[ https://issues.apache.org/jira/browse/OAK-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitul updated OAK-10455: Summary: synchronous commit (was: Data synchronisation between two pods) > synchronous commit > -- > > Key: OAK-10455 > URL: https://issues.apache.org/jira/browse/OAK-10455 > Project: Jackrabbit Oak > Issue Type: Bug > Components: commons >Affects Versions: 1.48.0 >Reporter: Nitul >Priority: Blocker > > We are using 1.48.0 version of oak-jcr. Out application stores the nodes and > retrive it. > We are using multiple pods of this application. and consider below scenario > which is creating issue. > > *Issue:* > We have two request as below: > Create some node and save it.- this is routed from pod1. (this will be saved > into mongo db after 1000ms with BackgroundUpdateOperation thread) > Get created nodes - this is routed from pod2. (As this second request > immediately executed, for pod2 recently created data is not available. ) > How we can commit the changes in synchronised manner. > > *Code:* > {code:java} > LeaseCheckMode leaseCheckMode = Boolean.TRUE.equals(enableLeaseCheck) ? > LeaseCheckMode.STRICT > : LeaseCheckMode.DISABLED; > documentNodeStore = new MongoDocumentNodeStoreBuilder() > .setMongoDB(getMongoURI(), mongoDbName, 16) > .setLeaseCheckMode(leaseCheckMode) > .build(); >Repository repository = new Jcr(new > Oak(documentNodeStore)).createRepository(); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10455) Synchronous commit
[ https://issues.apache.org/jira/browse/OAK-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitul updated OAK-10455: Summary: Synchronous commit (was: synchronous commit) > Synchronous commit > -- > > Key: OAK-10455 > URL: https://issues.apache.org/jira/browse/OAK-10455 > Project: Jackrabbit Oak > Issue Type: Bug > Components: commons >Affects Versions: 1.48.0 >Reporter: Nitul >Priority: Blocker > > We are using 1.48.0 version of oak-jcr. Out application stores the nodes and > retrive it. > We are using multiple pods of this application. and consider below scenario > which is creating issue. > > *Issue:* > We have two request as below: > Create some node and save it.- this is routed from pod1. (this will be saved > into mongo db after 1000ms with BackgroundUpdateOperation thread) > Get created nodes - this is routed from pod2. (As this second request > immediately executed, for pod2 recently created data is not available. ) > How we can commit the changes in synchronised manner. > > *Code:* > {code:java} > LeaseCheckMode leaseCheckMode = Boolean.TRUE.equals(enableLeaseCheck) ? > LeaseCheckMode.STRICT > : LeaseCheckMode.DISABLED; > documentNodeStore = new MongoDocumentNodeStoreBuilder() > .setMongoDB(getMongoURI(), mongoDbName, 16) > .setLeaseCheckMode(leaseCheckMode) > .build(); >Repository repository = new Jcr(new > Oak(documentNodeStore)).createRepository(); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10455) Data synchronisation between two pods
Nitul created OAK-10455: --- Summary: Data synchronisation between two pods Key: OAK-10455 URL: https://issues.apache.org/jira/browse/OAK-10455 Project: Jackrabbit Oak Issue Type: Bug Components: commons Affects Versions: 1.48.0 Reporter: Nitul We are using 1.48.0 version of oak-jcr. Out application stores the nodes and retrive it. We are using multiple pods of this application. and consider below scenario which is creating issue. *Issue:* We have two request as below: Create some node and save it.- this is routed from pod1. (this will be saved into mongo db after 1000ms with BackgroundUpdateOperation thread) Get created nodes - this is routed from pod2. (As this second request immediately executed, for pod2 recently created data is not available. ) How we can commit the changes in synchronised manner. *Code:* {code:java} LeaseCheckMode leaseCheckMode = Boolean.TRUE.equals(enableLeaseCheck) ? LeaseCheckMode.STRICT : LeaseCheckMode.DISABLED; documentNodeStore = new MongoDocumentNodeStoreBuilder() .setMongoDB(getMongoURI(), mongoDbName, 16) .setLeaseCheckMode(leaseCheckMode) .build(); Repository repository = new Jcr(new Oak(documentNodeStore)).createRepository(); {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)