[jira] [Commented] (OAK-9983) Mention alternatives to large MVP
[ https://issues.apache.org/jira/browse/OAK-9983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628397#comment-17628397 ] Stefan Egli commented on OAK-9983: -- [PR added|https://github.com/apache/jackrabbit-oak/pull/744] > Mention alternatives to large MVP > - > > Key: OAK-9983 > URL: https://issues.apache.org/jira/browse/OAK-9983 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: docs >Reporter: Stefan Egli >Assignee: Stefan Egli >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9983) Mention alternatives to large MVP
Stefan Egli created OAK-9983: Summary: Mention alternatives to large MVP Key: OAK-9983 URL: https://issues.apache.org/jira/browse/OAK-9983 Project: Jackrabbit Oak Issue Type: Documentation Components: docs Reporter: Stefan Egli Assignee: Stefan Egli -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9982) oak-search-elastic: avoid direct use of Json.createObject
Fabrizio Fortino created OAK-9982: - Summary: oak-search-elastic: avoid direct use of Json.createObject Key: OAK-9982 URL: https://issues.apache.org/jira/browse/OAK-9982 Project: Jackrabbit Oak Issue Type: Bug Components: elastic-search, indexing Reporter: Fabrizio Fortino Assignee: Fabrizio Fortino This could lead to dependency issues at runtime. Safer to use Elasticseaech java client utilities. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-9960) oak-run command to download blobs from datastore
[ https://issues.apache.org/jira/browse/OAK-9960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino resolved OAK-9960. --- Fix Version/s: 1.46.0 Resolution: Fixed > oak-run command to download blobs from datastore > > > Key: OAK-9960 > URL: https://issues.apache.org/jira/browse/OAK-9960 > Project: Jackrabbit Oak > Issue Type: Task > Components: oak-run >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > Fix For: 1.46.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-7182) Make it possible to update Guava
[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628314#comment-17628314
]
Julian Reschke edited comment on OAK-7182 at 11/3/22 12:49 PM:
---
It appears there is new leakage:
{noformat}
oak-segment-tar/target/baseline.xml-
oak-segment-tar/target/baseline.xml-false
oak-segment-tar/target/baseline.xml-3.0.0
oak-segment-tar/target/baseline.xml-3.0.0
oak-segment-tar/target/baseline.xml-
3.0.0
oak-segment-tar/target/baseline.xml-
oak-segment-tar/target/baseline.xml- 3.0.0
oak-segment-tar/target/baseline.xml:
com.google.common.cache,org.apache.jackrabbit.oak.cache,org.apache.jackrabbit.oak.commons,org.apache.jackrabbit.oak.segment.spi.monitor,org.aes>
{noformat}
Not sure whether this is just because of using
org.apache.jackrabbit.oak.cache...
was (Author: reschke):
It appears there is new leakage:
{noformat}
oak-segment-tar/target/baseline.xml-
oak-segment-tar/target/baseline.xml-false
oak-segment-tar/target/baseline.xml-3.0.0
oak-segment-tar/target/baseline.xml-3.0.0
oak-segment-tar/target/baseline.xml-
3.0.0
oak-segment-tar/target/baseline.xml-
oak-segment-tar/target/baseline.xml- 3.0.0
oak-segment-tar/target/baseline.xml:
com.google.common.cache,org.apache.jackrabbit.oak.cache,org.apache.jackrabbit.oak.commons,org.apache.jackrabbit.oak.segment.spi.monitor,org.aes>
{noformat}
> Make it possible to update Guava
>
>
> Key: OAK-7182
> URL: https://issues.apache.org/jira/browse/OAK-7182
> Project: Jackrabbit Oak
> Issue Type: Wish
>Reporter: Julian Reschke
>Priority: Minor
> Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff,
> OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff,
> guava.diff
>
>
> We currently rely on Guava 15, and this affects all users of Oak because they
> essentially need to use the same version.
> This is an overall issue to investigate what would need to be done in Oak in
> order to make updates possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-7182) Make it possible to update Guava
[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628314#comment-17628314
]
Julian Reschke commented on OAK-7182:
-
It appears there is new leakage:
{noformat}
oak-segment-tar/target/baseline.xml-
oak-segment-tar/target/baseline.xml-false
oak-segment-tar/target/baseline.xml-3.0.0
oak-segment-tar/target/baseline.xml-3.0.0
oak-segment-tar/target/baseline.xml-
3.0.0
oak-segment-tar/target/baseline.xml-
oak-segment-tar/target/baseline.xml- 3.0.0
oak-segment-tar/target/baseline.xml:
com.google.common.cache,org.apache.jackrabbit.oak.cache,org.apache.jackrabbit.oak.commons,org.apache.jackrabbit.oak.segment.spi.monitor,org.aes>
{noformat}
> Make it possible to update Guava
>
>
> Key: OAK-7182
> URL: https://issues.apache.org/jira/browse/OAK-7182
> Project: Jackrabbit Oak
> Issue Type: Wish
>Reporter: Julian Reschke
>Priority: Minor
> Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff,
> OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff,
> guava.diff
>
>
> We currently rely on Guava 15, and this affects all users of Oak because they
> essentially need to use the same version.
> This is an overall issue to investigate what would need to be done in Oak in
> order to make updates possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-7182) Make it possible to update Guava
[ https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558439#comment-17558439 ] Julian Reschke edited comment on OAK-7182 at 11/3/22 12:43 PM: --- As far as I recall, we have all Guava-tainted APIs deprecated and replacements in place (unless somebody introduced new ones since). Before we can *remove* the deprecated APIs, we'll need to figure out the consequences of that in the projects that use Oak. Onfortunately, that doesn't get the attention it should. Once we have removed the deprecated APIs in Oak, we are free to decide on the next steps. was (Author: reschke): As far as I recall, we have all Guava-tainted APIs deprecated and replacements in place (unless somebody introduced new ones since). Before we can *remove* the deprecated APIs, we'll need to figure out the consequences of that in the projects that use Oak. Onfortunately, that doesn't get the attention it should. Once we have removedthe deprecated APIs in Oak, we are free to decide on the next steps. > Make it possible to update Guava > > > Key: OAK-7182 > URL: https://issues.apache.org/jira/browse/OAK-7182 > Project: Jackrabbit Oak > Issue Type: Wish >Reporter: Julian Reschke >Priority: Minor > Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff, > OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff, > guava.diff > > > We currently rely on Guava 15, and this affects all users of Oak because they > essentially need to use the same version. > This is an overall issue to investigate what would need to be done in Oak in > order to make updates possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9981) Add a option in purgecommand(oak-run) to skip purge operations on active base index
[ https://issues.apache.org/jira/browse/OAK-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-9981: --- Description: The index purge command should provide an option to not apply purge operations on active base index. was: The index purge command should provide an option to not apply purge operations on active base index. > Add a option in purgecommand(oak-run) to skip purge operations on active base > index > --- > > Key: OAK-9981 > URL: https://issues.apache.org/jira/browse/OAK-9981 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > > The index purge command should provide an option to not apply purge > operations on active base index. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9981) Add a option in purgecommand(oak-run) to skip purge operations on active base index
[ https://issues.apache.org/jira/browse/OAK-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-9981: --- Description: The index purge command should provide an option to not apply purge operations on active base index. > Add a option in purgecommand(oak-run) to skip purge operations on active base > index > --- > > Key: OAK-9981 > URL: https://issues.apache.org/jira/browse/OAK-9981 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > > The index purge command should provide an option to not apply purge > operations on active base index. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9981) Add a option in purgecommand(oak-run) to skip purge operations on active base index
Mohit Kataria created OAK-9981: -- Summary: Add a option in purgecommand(oak-run) to skip purge operations on active base index Key: OAK-9981 URL: https://issues.apache.org/jira/browse/OAK-9981 Project: Jackrabbit Oak Issue Type: Bug Components: indexing Reporter: Mohit Kataria Assignee: Mohit Kataria -- This message was sent by Atlassian Jira (v8.20.10#820010)
