[jira] [Created] (OAK-10108) Build Jackrabbit/jackrabbit-oak-trunk #820 failed

2023-02-06 Thread Hudson (Jira)
Hudson created OAK-10108:


 Summary: Build Jackrabbit/jackrabbit-oak-trunk #820 failed
 Key: OAK-10108
 URL: https://issues.apache.org/jira/browse/OAK-10108
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

The build Jackrabbit/jackrabbit-oak-trunk #820 has failed.
First failed run: [Jackrabbit/jackrabbit-oak-trunk 
#820|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/820/] 
[console 
log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/820/console]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OAK-10107) update javdoc of class org.apache.jackrabbit.oak.plugins.nodetype.write.ReadWriteNodeTypeManager

2023-02-06 Thread Juerg Meier (Jira)
Juerg Meier created OAK-10107:
-

 Summary: update javdoc of class 
org.apache.jackrabbit.oak.plugins.nodetype.write.ReadWriteNodeTypeManager
 Key: OAK-10107
 URL: https://issues.apache.org/jira/browse/OAK-10107
 Project: Jackrabbit Oak
  Issue Type: Documentation
  Components: docs
Reporter: Juerg Meier


javadoc requires update as it currently inherits from 
[ReadOnlyNodeTypeManager|https://jackrabbit.apache.org/oak/docs/apidocs/org/apache/jackrabbit/oak/plugins/nodetype/ReadOnlyNodeTypeManager.html].

Consequently, methods registerNodeType() and unregisterNodeType() are said to 
throw an UnsupportedRepositoryOperationException, which is not the case. This 
methods work according to the JCR spec.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OAK-10106) Guava deprecations: set minimal logging level to 'warn'

2023-02-06 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-10106:
-
Fix Version/s: 1.52.0
   (was: 1.50.0)

> Guava deprecations: set minimal logging level to 'warn'
> ---
>
> Key: OAK-10106
> URL: https://issues.apache.org/jira/browse/OAK-10106
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: commons, core, core-spi
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.52.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OAK-10106) Guava deprecations: set minimal logging level to 'warn'

2023-02-06 Thread Julian Reschke (Jira)
Julian Reschke created OAK-10106:


 Summary: Guava deprecations: set minimal logging level to 'warn'
 Key: OAK-10106
 URL: https://issues.apache.org/jira/browse/OAK-10106
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: commons, core, core-spi
Reporter: Julian Reschke
Assignee: Julian Reschke
 Fix For: 1.50.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OAK-10105) Guava deprecations: set minimal logging level to 'info'

2023-02-06 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-10105:
-
Summary: Guava deprecations: set minimal logging level to 'info'  (was: 
GuavaDeprecations: set minimal logging level to 'info')

> Guava deprecations: set minimal logging level to 'info'
> ---
>
> Key: OAK-10105
> URL: https://issues.apache.org/jira/browse/OAK-10105
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: commons, core, core-spi
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.50.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OAK-10105) GuavaDeprecations: set minimal logging level to 'info'

2023-02-06 Thread Julian Reschke (Jira)
Julian Reschke created OAK-10105:


 Summary: GuavaDeprecations: set minimal logging level to 'info'
 Key: OAK-10105
 URL: https://issues.apache.org/jira/browse/OAK-10105
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: commons, core, core-spi
Reporter: Julian Reschke
Assignee: Julian Reschke
 Fix For: 1.50.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OAK-10104) Extend version consistency check

2023-02-06 Thread Marcel Reutegger (Jira)
Marcel Reutegger created OAK-10104:
--

 Summary: Extend version consistency check
 Key: OAK-10104
 URL: https://issues.apache.org/jira/browse/OAK-10104
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: run
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger


The version consistency check in oak-run currently resolves jcr:baseVersion and 
jcr:versionHistory references on versionable nodes and reports them when the 
target node does not exist. The check should be enhanced to also check if the 
target node has the expected jcr:uuid property value.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (OAK-9989) introduce oak-wrapped-guava project

2023-02-06 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684725#comment-17684725
 ] 

Julian Reschke commented on OAK-9989:
-

Work in progress, see https://github.com/apache/jackrabbit-oak/pull/841 - 
changes in document-store just for proof-of-concept purposes.

Questions:

- Can we generate Javadoc for the shaded lib? If so, should we? And if we do, 
can we modify it with warnings about where to use?

- Should we try to minimize the library?

> introduce oak-wrapped-guava project
> ---
>
> Key: OAK-9989
> URL: https://issues.apache.org/jira/browse/OAK-9989
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (OAK-10102) Disable lazy index download by default

2023-02-06 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684665#comment-17684665
 ] 

Thomas Mueller commented on OAK-10102:
--

[~joerghoh] Yes I think we can remove the code. But I'm not in a hurry to do 
that; possibly there are still some active uses.

> Disable lazy index download by default
> --
>
> Key: OAK-10102
> URL: https://issues.apache.org/jira/browse/OAK-10102
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene, query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
>
> I found that with the default settings (the system property 
> "oak.lucene.nonLazyIndex" not set), and a decent number of Lucene indexes, 
> each query that might use a Lucene index takes around 30 ms. With the 
> property set, each query takes only 2 ms or so.
> The lazy index download was meant to speed up startup, because only indexes 
> are downloaded that are actually needed. But on my side, I have disabled the 
> setting since then.
> I think it makes sense to set change the default value, like it was before. 
> So enable the system property  "oak.lucene.nonLazyIndex" by default.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (OAK-10102) Disable lazy index download by default

2023-02-06 Thread Joerg Hoh (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684647#comment-17684647
 ] 

Joerg Hoh commented on OAK-10102:
-

[~thomasm] agree on your reasons.

Should we then remove the code for lazy index download? Are there any 
circumstances where it still makes sense to use it?

> Disable lazy index download by default
> --
>
> Key: OAK-10102
> URL: https://issues.apache.org/jira/browse/OAK-10102
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene, query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
>
> I found that with the default settings (the system property 
> "oak.lucene.nonLazyIndex" not set), and a decent number of Lucene indexes, 
> each query that might use a Lucene index takes around 30 ms. With the 
> property set, each query takes only 2 ms or so.
> The lazy index download was meant to speed up startup, because only indexes 
> are downloaded that are actually needed. But on my side, I have disabled the 
> setting since then.
> I think it makes sense to set change the default value, like it was before. 
> So enable the system property  "oak.lucene.nonLazyIndex" by default.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Comment Edited] (OAK-7182) Make it possible to update Guava

2023-02-06 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684580#comment-17684580
 ] 

Julian Reschke edited comment on OAK-7182 at 2/6/23 10:47 AM:
--

h2. Roadmap (as of February 2023)

h3. OAK 1.48.0 (January 2023)

- bump up default logging levels for deprecated APIs to "warn" (OAK-10047)

h3. OAK 1.50.0 (March 2023)

- switch to Java 11 und use "forRemoval" deprecations for APIs exposing Guava 
(OAK-10007)
- bump up default logging levels for deprecated APIs to "error" (OAK-10086)

h3. OAK 1.52.0 (May 2023)

- introduce wrapped Guava project for Oak-internal use (OAK-9989)

h3. OAK 1.54.0

- remove deprecated APIs exposing Guava






was (Author: reschke):
h2. Roadmap (as of February 2023)

h3. OAK 1.48.0

- bump up default logging levels for deprecated APIs to "warn" (OAK-10047)

h3. OAK 1.50.0 (March 2023)

- switch to Java 11 und use "forRemoval" deprecations for APIs exposing Guava 
(OAK-10007)
- bump up default logging levels for deprecated APIs to "error" (OAK-10086)

h3. OAK 1.52.0 (May 2023)

- introduce wrapped Guava project for Oak-internal use (OAK-9989)

h3. OAK 1.54.0

- remove deprecated APIs exposing Guava





> 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

2023-02-06 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684580#comment-17684580
 ] 

Julian Reschke edited comment on OAK-7182 at 2/6/23 10:47 AM:
--

h2. Roadmap (as of February 2023)

h3. OAK 1.48.0

- bump up default logging levels for deprecated APIs to "warn" (OAK-10047)

h3. OAK 1.50.0 (March 2023)

- switch to Java 11 und use "forRemoval" deprecations for APIs exposing Guava 
(OAK-10007)
- bump up default logging levels for deprecated APIs to "error" (OAK-10086)

h3. OAK 1.52.0 (May 2023)

- introduce wrapped Guava project for Oak-internal use (OAK-9989)

h3. OAK 1.54.0

- remove deprecated APIs exposing Guava






was (Author: reschke):
h2. Plan (as of February 2023)

h3. OAK 1.48.0

- bump up default logging levels for deprecated APIs to "warn" (OAK-10047)

h3. OAK 1.50.0 (March 2023)

- switch to Java 11 und use "forRemoval" deprecations for APIs exposing Guava 
(OAK-10007)
- bump up default logging levels for deprecated APIs to "error" (OAK-10086)




> 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

2023-02-06 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17684580#comment-17684580
 ] 

Julian Reschke commented on OAK-7182:
-

h2. Plan (as of February 2023)

h3. OAK 1.48.0

- bump up default logging levels for deprecated APIs to "warn" (OAK-10047)

h3. OAK 1.50.0 (March 2023)

- switch to Java 11 und use "forRemoval" deprecations for APIs exposing Guava 
(OAK-10007)
- bump up default logging levels for deprecated APIs to "error" (OAK-10086)




> 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)