[jira] [Commented] (OAK-7165) Update baseline comparison version to latest stable 1.8.0

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7165:
-

Like https://issues.apache.org/jira/secure/attachment/12906469/OAK-7165.diff ?

> Update baseline comparison version to latest stable 1.8.0
> -
>
> Key: OAK-7165
> URL: https://issues.apache.org/jira/browse/OAK-7165
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-7165.diff
>
>
> 1.6.2 -> 1.8.0
>  
> Right? [~mreutegg], [~chetanm]?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7165) Update baseline comparison version to latest stable 1.8.0

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7165:

Attachment: OAK-7165.diff

> Update baseline comparison version to latest stable 1.8.0
> -
>
> Key: OAK-7165
> URL: https://issues.apache.org/jira/browse/OAK-7165
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-7165.diff
>
>
> 1.6.2 -> 1.8.0
>  
> Right? [~mreutegg], [~chetanm]?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7167:
-

1.0: [r1821405|http://svn.apache.org/r1821405]


> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke resolved OAK-7167.
-
Resolution: Fixed

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-6812:
-

trunk: [r1821404|http://svn.apache.org/r1821404]


> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6812-b.diff, OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Julian Reschke (JIRA)]

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

Julian Reschke resolved OAK-6812.
-
   Resolution: Fixed
Fix Version/s: 1.10
   1.9.0

> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6812-b.diff, OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-6812:

Labels: candidate_oak_1_8  (was: )

> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-6812-b.diff, OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7170) Port OSGiIT.bundleStates() test back to 1.0

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7170:
-

1.0: [r1821397|http://svn.apache.org/r1821397]


> Port OSGiIT.bundleStates() test back to 1.0
> ---
>
> Key: OAK-7170
> URL: https://issues.apache.org/jira/browse/OAK-7170
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: it
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> (this test was introduced for OAK-2402)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7175) Reduce cache misses on local diff-cache

[Marcel Reutegger (JIRA)]

Marcel Reutegger created OAK-7175:
-

 Summary: Reduce cache misses on local diff-cache
 Key: OAK-7175
 URL: https://issues.apache.org/jira/browse/OAK-7175
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: documentmk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
 Fix For: 1.10


There are quite some cache misses on the local diff-cache when there are 
external changes because the TieredDiffCache first checks the local diff-cache. 
The majority of calls can indeed be served from the local diff-cache, because 
local commits are usually more frequent than external changes that come in once 
a second. The cache misses could be avoided if there was a hint what kind of 
change the diff is based on.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6964) Document tail compaction

[JIRA]

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

Michael Dürig commented on OAK-6964:


Documented tail compaction, checkpoint compaction and log messages at 
[http://svn.apache.org/viewvc?rev=1821393=rev.]

To be done: configuration, scheduling.

> Document tail compaction
> 
>
> Key: OAK-6964
> URL: https://issues.apache.org/jira/browse/OAK-6964
> Project: Jackrabbit Oak
>  Issue Type: Documentation
>  Components: doc, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
>  Labels: documentation
> Fix For: 1.9.0, 1.10
>
>
> We need to add documentation of tail compaction:
> * What is it, how does it work?
> * How is it configured and scheduled?
> * How can it be monitored, what are the related log entries?
> * What are its limitations?
> * What if it fails?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7024) java.security.acl deprecated in Java 10, marked for removal in Java 11

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7024:
-

FWIW, I plan to do a Jackrabbit trunk release early February, but if needed we 
can do it earlier.

> java.security.acl deprecated in Java 10, marked for removal in Java 11
> --
>
> Key: OAK-7024
> URL: https://issues.apache.org/jira/browse/OAK-7024
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: security
>Reporter: Julian Reschke
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 1.10
>
>
> See  and 
> .
> Need to understand how this affects public Oak APIs, and what to do with them 
> on Java 11 (which will be an LTS release we probably need to support with Oak 
> 1.10).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7024) java.security.acl deprecated in Java 10, marked for removal in Java 11

[Alex Deparvu (JIRA)]

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

Alex Deparvu commented on OAK-7024:
---

I have updated the wip branch with a cleaner solution: provide default methods 
for PrincipalProvider so implementors of this code (1) can update at their 
convenience and (2) can remove all references of acl.Group from their code in 
preparation of the removal.
Still one thing that's bugging me is, I'm not sure I've fully managed to bypass 
the need to have this code updated twice: once to the transition version and 
once to the version that has no more reference to the Group interface.

Also, had a discussion with [~anchela] and we seem to agree that the new Group 
interface should exist on the jackrabbit api side to cover needs for both oak 
and jackrabbit, which means that JCR-4246 might to come first, or at least we'd 
have to create a dedicated issue for the introduction of the new interface (and 
wait for a jackrabbit release). FYI [~reschke].

Feedback appreciated!


> java.security.acl deprecated in Java 10, marked for removal in Java 11
> --
>
> Key: OAK-7024
> URL: https://issues.apache.org/jira/browse/OAK-7024
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: security
>Reporter: Julian Reschke
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 1.10
>
>
> See  and 
> .
> Need to understand how this affects public Oak APIs, and what to do with them 
> on Java 11 (which will be an LTS release we probably need to support with Oak 
> 1.10).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-2374) Sporadic test failure of OSGiIT.listBundles on Buildbot

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-2374:
-

trunk: [r1784526|http://svn.apache.org/r1784526] 
[r1646783|http://svn.apache.org/r1646783]
1.0: [r1821388|http://svn.apache.org/r1821388]


> Sporadic test failure of OSGiIT.listBundles on Buildbot
> ---
>
> Key: OAK-2374
> URL: https://issues.apache.org/jira/browse/OAK-2374
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: it
>Reporter: Michael Dürig
>Assignee: Chetan Mehrotra
>Priority: Minor
>  Labels: CI, buildbot, test
> Fix For: 1.3.0, 1.4
>
> Attachments: OAK-2374.patch
>
>
> See http://markmail.org/message/idx2y2dwpkaxchsp for previous mention.
> I suggest to use the mechanism from OAK-2371 to exclude the tests on that CI 
> environment for now. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7174) The check command returns a zero exit code on error

[Francesco Mari (JIRA)]

Francesco Mari created OAK-7174:
---

 Summary: The check command returns a zero exit code on error
 Key: OAK-7174
 URL: https://issues.apache.org/jira/browse/OAK-7174
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: run, segment-tar
Reporter: Francesco Mari
Assignee: Francesco Mari
 Fix For: 1.10


The check command should return a non-zero exit code if it fails with an 
exception. Moreover, every error message should be printed on the standard 
error.





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7171) The history command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7171:

Fix Version/s: 1.8.1

> The history command returns a zero exit code on error
> -
>
> Key: OAK-7171
> URL: https://issues.apache.org/jira/browse/OAK-7171
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10, 1.8.1
>
>
> The history command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7171) The history command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari commented on OAK-7171:
-

Backported to 1.8 at r1821379.

> The history command returns a zero exit code on error
> -
>
> Key: OAK-7171
> URL: https://issues.apache.org/jira/browse/OAK-7171
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> The history command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-6812:
-

Proposed patch updated accordingly.

> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-6812-b.diff, OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7172) Document TarMK specific MBeans

[JIRA]

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

Michael Dürig updated OAK-7172:
---
Description: Currently the [TarMK 
documentation|http://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#monitoring-via-jmx]
 only mentions {{SegmentRevisionGarbageCollection}}. We should review that 
paragraph and also include documentation for all other relevant JMX endpoints.

> Document TarMK specific MBeans
> --
>
> Key: OAK-7172
> URL: https://issues.apache.org/jira/browse/OAK-7172
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: doc, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
>  Labels: documentation
> Fix For: 1.9.0, 1.10
>
>
> Currently the [TarMK 
> documentation|http://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#monitoring-via-jmx]
>  only mentions {{SegmentRevisionGarbageCollection}}. We should review that 
> paragraph and also include documentation for all other relevant JMX endpoints.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7172) Document TarMK specific MBeans

[JIRA]

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

Michael Dürig updated OAK-7172:
---
Environment: (was: Currently the [TarMK 
documentation|http://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#monitoring-via-jmx]
 only mentions {{SegmentRevisionGarbageCollection}}. We should review that 
paragraph and also include documentation for all other relevant JMX endpoints.)

> Document TarMK specific MBeans
> --
>
> Key: OAK-7172
> URL: https://issues.apache.org/jira/browse/OAK-7172
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: doc, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
>  Labels: documentation
> Fix For: 1.9.0, 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7169) The datastorecheck returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari commented on OAK-7169:
-

Backported to 1.8 at r1821378.

> The datastorecheck returns a zero exit code on error
> 
>
> Key: OAK-7169
> URL: https://issues.apache.org/jira/browse/OAK-7169
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> The datastorecheck command should return a non-zero exit code if it fails 
> with an exception. Moreover, every error message should be printed on the 
> standard error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7173) Update documentation for oak-run check

[JIRA]

Michael Dürig created OAK-7173:
--

 Summary: Update documentation for oak-run check
 Key: OAK-7173
 URL: https://issues.apache.org/jira/browse/OAK-7173
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: oak-run, doc, segment-tar
Reporter: Michael Dürig
Assignee: Andrei Dulceanu
 Fix For: 1.9.0, 1.10


We should review and update the documentation of [{{oak-run 
check}}|http://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#check].
 E.g. to include the new options from OAK-6373.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-6812:

Attachment: OAK-6812-b.diff

> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-6812-b.diff, OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Fix Version/s: 1.8.1

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10, 1.8.1
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari commented on OAK-7168:
-

Backported to 1.8 at r1821377.

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10, 1.8.1
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7153) Avoid persistent cache read access when key is not cached

[Marcel Reutegger (JIRA)]

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

Marcel Reutegger resolved OAK-7153.
---
   Resolution: Fixed
Fix Version/s: 1.9.0

Implemented in trunk: http://svn.apache.org/r1821373

> Avoid persistent cache read access when key is not cached
> -
>
> Key: OAK-7153
> URL: https://issues.apache.org/jira/browse/OAK-7153
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.9.0, 1.10
>
>
> OAK-6803 introduced a way to configure the persistent cache with a predicate 
> to decide whether a key should be cached. The same predicate can be used to 
> determine whether a read on the persistent cache should be attempted at all. 
> If a key is never cached, the read can be avoided because it will never 
> return a value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7172) Document TarMK specific MBeans

[JIRA]

Michael Dürig created OAK-7172:
--

 Summary: Document TarMK specific MBeans
 Key: OAK-7172
 URL: https://issues.apache.org/jira/browse/OAK-7172
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: doc, segment-tar
 Environment: Currently the [TarMK 
documentation|http://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#monitoring-via-jmx]
 only mentions {{SegmentRevisionGarbageCollection}}. We should review that 
paragraph and also include documentation for all other relevant JMX endpoints.
Reporter: Michael Dürig
Assignee: Michael Dürig
 Fix For: 1.9.0, 1.10






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7131) xpath to sql2 conversion drops order by clause for some cases

[Vikas Saurabh (JIRA)]

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

Vikas Saurabh updated OAK-7131:
---
Fix Version/s: 1.9.0

> xpath to sql2 conversion drops order by clause for some cases
> -
>
> Key: OAK-7131
> URL: https://issues.apache.org/jira/browse/OAK-7131
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: query
>Reporter: Vikas Saurabh
>Assignee: Thomas Mueller
>Priority: Critical
> Fix For: 1.9.0, 1.10
>
>
> When xpath has OR-ed primary type and a couple of OR-ed property constraint 
> (e.g. \[0]), the converted sql statement doesn't get ordering clause.
> \[0]:
> {noformat}
> //(element(*, type1) | element(*, type2))[@a='b' or @c='d'] order by @foo
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7171) The history command returns a zero exit code on error

[Francesco Mari (JIRA)]

Francesco Mari created OAK-7171:
---

 Summary: The history command returns a zero exit code on error
 Key: OAK-7171
 URL: https://issues.apache.org/jira/browse/OAK-7171
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: run, segment-tar
Reporter: Francesco Mari
Assignee: Francesco Mari
 Fix For: 1.10


The history command should return a non-zero exit code if it fails with an 
exception. Moreover, every error message should be printed on the standard 
error.





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7169) The datastorecheck returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari resolved OAK-7169.
-
Resolution: Fixed

> The datastorecheck returns a zero exit code on error
> 
>
> Key: OAK-7169
> URL: https://issues.apache.org/jira/browse/OAK-7169
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> The datastorecheck command should return a non-zero exit code if it fails 
> with an exception. Moreover, every error message should be printed on the 
> standard error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari resolved OAK-7168.
-
Resolution: Fixed

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7163) Upgrade commons-io dependency to 2.6

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7163:

Fix Version/s: (was: 1.9.0)

> Upgrade commons-io dependency to 2.6
> 
>
> Key: OAK-7163
> URL: https://issues.apache.org/jira/browse/OAK-7163
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Labels: candidate_oak_1_8  (was: )

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OAK-7163) Upgrade commons-io dependency to 2.6

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on OAK-7163 at 1/17/18 2:42 PM:
--

trunk: [r1821372|http://svn.apache.org/r1821372] 
[r1821245|http://svn.apache.org/r1821245]



was (Author: reschke):
trunk: [r1821245|http://svn.apache.org/r1821245]

> Upgrade commons-io dependency to 2.6
> 
>
> Key: OAK-7163
> URL: https://issues.apache.org/jira/browse/OAK-7163
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7169) The datastorecheck returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7169:

Labels: candidate_oak_1_8  (was: )

> The datastorecheck returns a zero exit code on error
> 
>
> Key: OAK-7169
> URL: https://issues.apache.org/jira/browse/OAK-7169
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> The datastorecheck command should return a non-zero exit code if it fails 
> with an exception. Moreover, every error message should be printed on the 
> standard error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7169) The datastorecheck returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7169:

Fix Version/s: 1.9.0

> The datastorecheck returns a zero exit code on error
> 
>
> Key: OAK-7169
> URL: https://issues.apache.org/jira/browse/OAK-7169
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> The datastorecheck command should return a non-zero exit code if it fails 
> with an exception. Moreover, every error message should be printed on the 
> standard error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7169) The datastorecheck returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari commented on OAK-7169:
-

Fixed at r1821370.

> The datastorecheck returns a zero exit code on error
> 
>
> Key: OAK-7169
> URL: https://issues.apache.org/jira/browse/OAK-7169
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> The datastorecheck command should return a non-zero exit code if it fails 
> with an exception. Moreover, every error message should be printed on the 
> standard error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7170) Port OSGiIT.bundleStates() test back to 1.0

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7170:

Description: (this test was introduced for OAK-2402)  (was: (this test was 
introduces for OAK-2402))

> Port OSGiIT.bundleStates() test back to 1.0
> ---
>
> Key: OAK-7170
> URL: https://issues.apache.org/jira/browse/OAK-7170
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: it
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> (this test was introduced for OAK-2402)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7170) Port OSGiIT.bundleStates() test back to 1.0

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7170:

Description: (this test was introduces for OAK-2402)

> Port OSGiIT.bundleStates() test back to 1.0
> ---
>
> Key: OAK-7170
> URL: https://issues.apache.org/jira/browse/OAK-7170
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: it
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> (this test was introduces for OAK-2402)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7170) Port OSGiIT.bundleStates() test back to 1.0

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7170:

Summary: Port OSGiIT.bundleStates() test back to 1.0  (was: Port 
OSGiIT.bundleStates test back to 1.0)

> Port OSGiIT.bundleStates() test back to 1.0
> ---
>
> Key: OAK-7170
> URL: https://issues.apache.org/jira/browse/OAK-7170
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: it
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7170) Port OSGiIT.bundleStates test back to 1.0

[Julian Reschke (JIRA)]

Julian Reschke created OAK-7170:
---

 Summary: Port OSGiIT.bundleStates test back to 1.0
 Key: OAK-7170
 URL: https://issues.apache.org/jira/browse/OAK-7170
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: it
Affects Versions: 1.0.40
Reporter: Julian Reschke
Assignee: Julian Reschke
 Fix For: 1.0.41






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-2402) oak-lucene fails to start in OSGi

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-2402:

Description: 
since the refactorings of OAK-2307, oak-lucene cannot resolve all the required 
classes in an OSGi environment and fails to start.

OSGiIT fails to detect it.

  was:
since the refactorings of OAK-2307, oak-lucene cannot resolve all the required 
classes in an OSGi environemnt and fails to start.

OSGiIT fails to detect it.


> oak-lucene fails to start in OSGi
> -
>
> Key: OAK-2402
> URL: https://issues.apache.org/jira/browse/OAK-2402
> Project: Jackrabbit Oak
>  Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Chetan Mehrotra
>Priority: Blocker
> Fix For: 1.1.5
>
> Attachments: OAK-2402-test.patch
>
>
> since the refactorings of OAK-2307, oak-lucene cannot resolve all the 
> required classes in an OSGi environment and fails to start.
> OSGiIT fails to detect it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7169) The datastorecheck returns a zero exit code on error

[Francesco Mari (JIRA)]

Francesco Mari created OAK-7169:
---

 Summary: The datastorecheck returns a zero exit code on error
 Key: OAK-7169
 URL: https://issues.apache.org/jira/browse/OAK-7169
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: run
Reporter: Francesco Mari
Assignee: Francesco Mari
 Fix For: 1.10


The datastorecheck command should return a non-zero exit code if it fails with 
an exception. Moreover, every error message should be printed on the standard 
error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Issue Type: Bug  (was: Improvement)

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-2374) Sporadic test failure of OSGiIT.listBundles on Buildbot

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-2374:
-

...backporting the test case change to 1.0 to avoid merge conflicts for 
OAK-2402.

> Sporadic test failure of OSGiIT.listBundles on Buildbot
> ---
>
> Key: OAK-2374
> URL: https://issues.apache.org/jira/browse/OAK-2374
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: it
>Reporter: Michael Dürig
>Assignee: Chetan Mehrotra
>Priority: Minor
>  Labels: CI, buildbot, test
> Fix For: 1.3.0, 1.4
>
> Attachments: OAK-2374.patch
>
>
> See http://markmail.org/message/idx2y2dwpkaxchsp for previous mention.
> I suggest to use the mechanism from OAK-2371 to exclude the tests on that CI 
> environment for now. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Fix Version/s: 1.9.0

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari commented on OAK-7168:
-

Fixed at r1821362.

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-4689) Add information about amount of data vs. waste to oak-run

[JIRA]

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

Michael Dürig updated OAK-4689:
---
Fix Version/s: (was: 1.9.0)

> Add information about amount of data vs. waste to oak-run
> -
>
> Key: OAK-4689
> URL: https://issues.apache.org/jira/browse/OAK-4689
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: run, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
>  Labels: production, tooling
> Fix For: 1.10
>
>
> This is a follow up for OAK-3695, where we decided that it would be to 
> expensive doing this as live monitoring. 
> Instead we should add functionality to {{oak-run}} that could connect in read 
> only mode to a running repository and collect information about how much data 
> and how must wast the repository contains. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OAK-7075) Document oak-run compact arguments and system properties

[JIRA]

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

Michael Dürig resolved OAK-7075.

Resolution: Fixed

Fixed at http://svn.apache.org/viewvc?rev=1821361=rev

> Document oak-run compact arguments and system properties
> 
>
> Key: OAK-7075
> URL: https://issues.apache.org/jira/browse/OAK-7075
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: doc, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
>  Labels: documentation
> Fix For: 1.9.0, 1.10
>
>
> Ensure {{oak-doc}} is up to date with the current version of {{oak-run 
> compact}}, its current command line arguments and system properties. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OAK-7163) Upgrade commons-io dependency to 2.6

[Julian Reschke (JIRA)]

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

Julian Reschke reopened OAK-7163:
-

> Upgrade commons-io dependency to 2.6
> 
>
> Key: OAK-7163
> URL: https://issues.apache.org/jira/browse/OAK-7163
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OAK-7160) Update commons-codec dependency

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on OAK-7160 at 1/17/18 1:33 PM:
--

trunk: [r1821360|http://svn.apache.org/r1821360] 
[r1821221|http://svn.apache.org/r1821221]



was (Author: reschke):
trunk: [r1821221|http://svn.apache.org/r1821221]

> Update commons-codec dependency
> ---
>
> Key: OAK-7160
> URL: https://issues.apache.org/jira/browse/OAK-7160
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OAK-7160) Update commons-codec dependency

[Julian Reschke (JIRA)]

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

Julian Reschke reopened OAK-7160:
-

> Update commons-codec dependency
> ---
>
> Key: OAK-7160
> URL: https://issues.apache.org/jira/browse/OAK-7160
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari reassigned OAK-7168:
---

Assignee: Francesco Mari

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Fix Version/s: 1.10

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Priority: Major
> Fix For: 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Component/s: run

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Priority: Major
> Fix For: 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Description: The debug command should return a non-zero exit code if it 
fails with an exception. Moreover, every error message should be printed on the 
standard error.

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run, segment-tar
>Reporter: Francesco Mari
>Priority: Major
> Fix For: 1.10
>
>
> The debug command should return a non-zero exit code if it fails with an 
> exception. Moreover, every error message should be printed on the standard 
> error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

Francesco Mari created OAK-7168:
---

 Summary: The debug command returns a zero exit code on error
 Key: OAK-7168
 URL: https://issues.apache.org/jira/browse/OAK-7168
 Project: Jackrabbit Oak
  Issue Type: Improvement
Reporter: Francesco Mari






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7168) The debug command returns a zero exit code on error

[Francesco Mari (JIRA)]

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

Francesco Mari updated OAK-7168:

Component/s: segment-tar

> The debug command returns a zero exit code on error
> ---
>
> Key: OAK-7168
> URL: https://issues.apache.org/jira/browse/OAK-7168
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7167:
-

OK, I'll give it a try.

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke reassigned OAK-7167:
---

Assignee: Julian Reschke

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on OAK-7167 at 1/17/18 1:10 PM:
--

[~chetanm] - just the test? (as in http://svn.apache.org/r1652100 and 
http://svn.apache.org/r1652132)


was (Author: reschke):
[~chetanm] - just the test? (as in 
http://svn.apache.org/viewvc?view=revision=1652132 ?)

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-2402) oak-lucene fails to start in OSGi

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-2402:
-

trunk: [r1652132|http://svn.apache.org/r1652132] 
[r1652131|http://svn.apache.org/r1652131] 
[r1652100|http://svn.apache.org/r1652100]


> oak-lucene fails to start in OSGi
> -
>
> Key: OAK-2402
> URL: https://issues.apache.org/jira/browse/OAK-2402
> Project: Jackrabbit Oak
>  Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Chetan Mehrotra
>Priority: Blocker
> Fix For: 1.1.5
>
> Attachments: OAK-2402-test.patch
>
>
> since the refactorings of OAK-2307, oak-lucene cannot resolve all the 
> required classes in an OSGi environemnt and fails to start.
> OSGiIT fails to detect it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra commented on OAK-7167:
--

{quote}just the test?{quote}

Yes

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7131) xpath to sql2 conversion drops order by clause for some cases

[Thomas Mueller (JIRA)]

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

Thomas Mueller commented on OAK-7131:
-

http://svn.apache.org/r1821358 (trunk)

> xpath to sql2 conversion drops order by clause for some cases
> -
>
> Key: OAK-7131
> URL: https://issues.apache.org/jira/browse/OAK-7131
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: query
>Reporter: Vikas Saurabh
>Assignee: Thomas Mueller
>Priority: Critical
> Fix For: 1.10
>
>
> When xpath has OR-ed primary type and a couple of OR-ed property constraint 
> (e.g. \[0]), the converted sql statement doesn't get ordering clause.
> \[0]:
> {noformat}
> //(element(*, type1) | element(*, type2))[@a='b' or @c='d'] order by @foo
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7167:
-

[~chetanm] - just the test? (as in 
http://svn.apache.org/viewvc?view=revision=1652132 ?)

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7167:
-

In 1.2, this would be catched  in oak-it/osgi:

{noformat}
Apache Jackrabbit Oak
[main] INFO org.ops4j.pax.exam.spi.reactors.ReactorManager - suite finished
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.015 sec <<< 
FAILURE!
bundleStates(org.apache.jackrabbit.oak.osgi.OSGiIT)  Time elapsed: 0 sec  <<< 
FAILURE!
java.lang.AssertionError: Bundle org.apache.jackrabbit.oak-lucene [29] not 
active. have a look at the logs expected:<32> but was:<2>
{noformat}

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-4401) Excerpt Highlighting for a property is not correct

[Tommaso Teofili (JIRA)]

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

Tommaso Teofili commented on OAK-4401:
--

+1 LGTM

> Excerpt Highlighting for a property is not correct 
> ---
>
> Key: OAK-4401
> URL: https://issues.apache.org/jira/browse/OAK-4401
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: query
>Affects Versions: 1.5.2
>Reporter: Ankit Agarwal
>Assignee: Vikas Saurabh
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
> Attachments: 
> 0001-OAK-4401-Excerpt-Highlighting-for-a-property-is-not-.patch
>
>
> if we have following text at property 
> /jcr:content/text
> ===
> A state agency’s Conflict of Interest Code must reflect the current structure 
> of the organization and properly identify officials andemployees
> =
> and if rep:excerpt(/jcr:content/text) is been calling after search then 
> ==
> officials will be in output , which is incorrect.
> ==



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra commented on OAK-7167:
--

Looks like we need to backport the test introduced in OAK-2402 which was 
introduced for very same reason!

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-7167:
-

It would be good to understand why our testing did not detect this, and whether 
the same problem would have been detected in newer branches.

> 1.0: oak-lucene uses packages from oak-core that are not exported
> -
>
> Key: OAK-7167
> URL: https://issues.apache.org/jira/browse/OAK-7167
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.40
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 1.0.41
>
>
> See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7167) 1.0: oak-lucene uses packages from oak-core that are not exported

[Julian Reschke (JIRA)]

Julian Reschke created OAK-7167:
---

 Summary: 1.0: oak-lucene uses packages from oak-core that are not 
exported
 Key: OAK-7167
 URL: https://issues.apache.org/jira/browse/OAK-7167
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: core
Affects Versions: 1.0.40
Reporter: Julian Reschke
 Fix For: 1.0.41


See comments in https://issues.apache.org/jira/browse/OAK-5299.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-5885) segment-tar should have a tarmkrecovery command

[JIRA]

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

Michael Dürig updated OAK-5885:
---
Fix Version/s: (was: 1.9.0)

> segment-tar should have a tarmkrecovery command
> ---
>
> Key: OAK-5885
> URL: https://issues.apache.org/jira/browse/OAK-5885
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: run, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Michael Dürig
>Priority: Minor
>  Labels: candidate_oak_1_8, tooling
> Fix For: 1.10
>
>
> {{oak-segment}} had a {{tarmkrecovery}} command responsible with listing 
> candidates for head journal entries. We should re-enable this also for 
> {{oak-segment-tar}}.
> /cc [~mduerig] [~frm]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7166) Union with different selector names

[Thomas Mueller (JIRA)]

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

Thomas Mueller updated OAK-7166:

Description: 
The following query returns the wrong nodes:

{noformat}
/jcr:root/libs/(* | */* | */*/* | */*/*/* | */*/*/*/*)/install

select b.[jcr:path] as [jcr:path], b.[jcr:score] as [jcr:score], b.* from 
[nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 where ischildnode(a, '/libs') and name(b) = 'install' 
 union select c.[jcr:path] as [jcr:path], c.[jcr:score] as [jcr:score], c.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 where ischildnode(a, '/libs') and name(c) = 'install' 
 union select d.[jcr:path] as [jcr:path], d.[jcr:score] as [jcr:score], d.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 inner join [nt:base] as d on ischildnode(d, c)
 where ischildnode(a, '/libs') and name(d) = 'install' 
{noformat}

If I change the selector name to "x" in each subquery, then it works. There is 
no XPath version of this workaround:

{noformat}
select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* from 
[nt:base] as a
 inner join [nt:base] as x on ischildnode(x, a)
 where ischildnode(a, '/libs') and name(x) = 'install' 
 union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as x on ischildnode(x, b)
 where ischildnode(a, '/libs') and name(x) = 'install' 
 union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 inner join [nt:base] as x on ischildnode(x, c)
 where ischildnode(a, '/libs') and name(x) = 'install' 
{noformat}

Need to check if this is a Oak bug, or a bug in the query tool I use.

> Union with different selector names
> ---
>
> Key: OAK-7166
> URL: https://issues.apache.org/jira/browse/OAK-7166
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Fix For: 1.10
>
>
> The following query returns the wrong nodes:
> {noformat}
> /jcr:root/libs/(* | */* | */*/* | */*/*/* | */*/*/*/*)/install
> select b.[jcr:path] as [jcr:path], b.[jcr:score] as [jcr:score], b.* from 
> [nt:base] as a
>  inner join [nt:base] as b on ischildnode(b, a)
>  where ischildnode(a, '/libs') and name(b) = 'install' 
>  union select c.[jcr:path] as [jcr:path], c.[jcr:score] as [jcr:score], c.* 
> from [nt:base] as a
>  inner join [nt:base] as b on ischildnode(b, a)
>  inner join [nt:base] as c on ischildnode(c, b)
>  where ischildnode(a, '/libs') and name(c) = 'install' 
>  union select d.[jcr:path] as [jcr:path], d.[jcr:score] as [jcr:score], d.* 
> from [nt:base] as a
>  inner join [nt:base] as b on ischildnode(b, a)
>  inner join [nt:base] as c on ischildnode(c, b)
>  inner join [nt:base] as d on ischildnode(d, c)
>  where ischildnode(a, '/libs') and name(d) = 'install' 
> {noformat}
> If I change the selector name to "x" in each subquery, then it works. There 
> is no XPath version of this workaround:
> {noformat}
> select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* from 
> [nt:base] as a
>  inner join [nt:base] as x on ischildnode(x, a)
>  where ischildnode(a, '/libs') and name(x) = 'install' 
>  union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
> from [nt:base] as a
>  inner join [nt:base] as b on ischildnode(b, a)
>  inner join [nt:base] as x on ischildnode(x, b)
>  where ischildnode(a, '/libs') and name(x) = 'install' 
>  union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
> from [nt:base] as a
>  inner join [nt:base] as b on ischildnode(b, a)
>  inner join [nt:base] as c on ischildnode(c, b)
>  inner join [nt:base] as x on ischildnode(x, c)
>  where ischildnode(a, '/libs') and name(x) = 'install' 
> {noformat}
> Need to check if this is a Oak bug, or a bug in the query tool I use.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OAK-7166) Union with different selector names

[Thomas Mueller (JIRA)]

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

Thomas Mueller updated OAK-7166:

Environment: (was: The following query returns the wrong nodes:

{noformat}
/jcr:root/libs/(* | */* | */*/* | */*/*/* | */*/*/*/*)/install

select b.[jcr:path] as [jcr:path], b.[jcr:score] as [jcr:score], b.* from 
[nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 where ischildnode(a, '/libs') and name(b) = 'install' 
 union select c.[jcr:path] as [jcr:path], c.[jcr:score] as [jcr:score], c.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 where ischildnode(a, '/libs') and name(c) = 'install' 
 union select d.[jcr:path] as [jcr:path], d.[jcr:score] as [jcr:score], d.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 inner join [nt:base] as d on ischildnode(d, c)
 where ischildnode(a, '/libs') and name(d) = 'install' 
{noformat}

If I change the selector name to "x" in each subquery, then it works. There is 
no XPath version of this workaround:

{noformat}
select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* from 
[nt:base] as a
 inner join [nt:base] as x on ischildnode(x, a)
 where ischildnode(a, '/libs') and name(x) = 'install' 
 union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as x on ischildnode(x, b)
 where ischildnode(a, '/libs') and name(x) = 'install' 
 union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 inner join [nt:base] as x on ischildnode(x, c)
 where ischildnode(a, '/libs') and name(x) = 'install' 
{noformat}

Need to check if this is a Oak bug, or a bug in the query tool I use.)

> Union with different selector names
> ---
>
> Key: OAK-7166
> URL: https://issues.apache.org/jira/browse/OAK-7166
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Fix For: 1.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OAK-7166) Union with different selector names

[Thomas Mueller (JIRA)]

Thomas Mueller created OAK-7166:
---

 Summary: Union with different selector names
 Key: OAK-7166
 URL: https://issues.apache.org/jira/browse/OAK-7166
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: query
 Environment: The following query returns the wrong nodes:

{noformat}
/jcr:root/libs/(* | */* | */*/* | */*/*/* | */*/*/*/*)/install

select b.[jcr:path] as [jcr:path], b.[jcr:score] as [jcr:score], b.* from 
[nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 where ischildnode(a, '/libs') and name(b) = 'install' 
 union select c.[jcr:path] as [jcr:path], c.[jcr:score] as [jcr:score], c.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 where ischildnode(a, '/libs') and name(c) = 'install' 
 union select d.[jcr:path] as [jcr:path], d.[jcr:score] as [jcr:score], d.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 inner join [nt:base] as d on ischildnode(d, c)
 where ischildnode(a, '/libs') and name(d) = 'install' 
{noformat}

If I change the selector name to "x" in each subquery, then it works. There is 
no XPath version of this workaround:

{noformat}
select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* from 
[nt:base] as a
 inner join [nt:base] as x on ischildnode(x, a)
 where ischildnode(a, '/libs') and name(x) = 'install' 
 union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as x on ischildnode(x, b)
 where ischildnode(a, '/libs') and name(x) = 'install' 
 union select x.[jcr:path] as [jcr:path], x.[jcr:score] as [jcr:score], x.* 
from [nt:base] as a
 inner join [nt:base] as b on ischildnode(b, a)
 inner join [nt:base] as c on ischildnode(c, b)
 inner join [nt:base] as x on ischildnode(x, c)
 where ischildnode(a, '/libs') and name(x) = 'install' 
{noformat}

Need to check if this is a Oak bug, or a bug in the query tool I use.
Reporter: Thomas Mueller
Assignee: Thomas Mueller
 Fix For: 1.10






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Marcel Reutegger (JIRA)]

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

Marcel Reutegger commented on OAK-6812:
---

+1

> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OAK-6812) UpdateOp Condition: be consistent about the support for non-revision properties

[Julian Reschke (JIRA)]

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

Julian Reschke commented on OAK-6812:
-

Proposal: keep old behavior of {{containsMapEntry}} (being restricted to 
revision properties), and add {{contains}} (working for top-level properties).

> UpdateOp Condition: be consistent about the support for non-revision 
> properties
> ---
>
> Key: OAK-6812
> URL: https://issues.apache.org/jira/browse/OAK-6812
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-6812.diff
>
>
> For instance, EXISTS should be supported for non-revision properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)