[jira] [Commented] (OAK-10489) Build Jackrabbit/jackrabbit-oak-trunk #1192 failed
[ https://issues.apache.org/jira/browse/OAK-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774930#comment-17774930 ] Hudson commented on OAK-10489: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1194|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1194/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1194/console] > Build Jackrabbit/jackrabbit-oak-trunk #1192 failed > -- > > Key: OAK-10489 > URL: https://issues.apache.org/jira/browse/OAK-10489 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1192 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1192|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1192/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1192/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10491) Indexing: pass a MongoDatabase instance instead of MongoConnection to indexing logic
Nuno Santos created OAK-10491: - Summary: Indexing: pass a MongoDatabase instance instead of MongoConnection to indexing logic Key: OAK-10491 URL: https://issues.apache.org/jira/browse/OAK-10491 Project: Jackrabbit Oak Issue Type: Improvement Reporter: Nuno Santos The pipeline indexing strategy needs to have access to a MongoDatabase object to register a custom codec to deserialize the responses from Mongo. Previously we were passing a MongoConnection object which contained a reference to MongoDatabase. But the indexing job does not need any other fields from MongoConnection other than MongoDatabase. But requiring MongoConnection makes it harder for users of Oak to call this API. We can simplify the logic by requiring only a MongoConnection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10490) Suggest queries return duplicate entries if prefetch is enabled
[
https://issues.apache.org/jira/browse/OAK-10490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved OAK-10490.
--
Fix Version/s: 1.60.0
Resolution: Fixed
> Suggest queries return duplicate entries if prefetch is enabled
> ---
>
> Key: OAK-10490
> URL: https://issues.apache.org/jira/browse/OAK-10490
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Fix For: 1.60.0
>
>
> If prefetch is enabled, and prefetch count is larger than 0, then suggest
> queries return duplicate results.
> This seems to be caused by oak-search FulltextIndex.FulltextPathCursor:
> FulltextPathCursor.next() returns a new IndexRow that references currentRow.
> But pathIterator.next() updates currentRow. So that the following code can
> return different results:
> {noformat}
> // here, excerpt1 and except2 are different:
> IndexRow row1 = fulltextPathCursor.next();
> String excerpt1 = row1.getValue("rep:excerpt"));
> IndexRow row2 = fulltextPathCursor.next();
> String excerpt2 = row2.getValue("rep:excerpt"));
> // here, excerpt1 is equal to except2:
> IndexRow row1 = fulltextPathCursor.next();
> IndexRow row2 = fulltextPathCursor.next();
> String excerpt1 = row1.getValue("rep:excerpt"));
> String excerpt2 = row2.getValue("rep:excerpt"));
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774877#comment-17774877 ] Julian Reschke edited comment on OAK-6741 at 10/13/23 11:14 AM: Potentially helpful comparison tool: https://github.com/jsedding/osgi-ds-metatype-diff was (Author: reschke): Potentially helpful comparison tool. > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu >Priority: Major > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R6 annotations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774877#comment-17774877 ] Julian Reschke commented on OAK-6741: - Potentially helpful comparison tool. > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu >Priority: Major > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R6 annotations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
