[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=17432552#comment-17432552 ] Marco Piovesana commented on OAK-7182: -- [~reschke] I was trying to understand what needs to be done for OAK-8717. I've seen that it does already contain a patch, it hasn't been merged because it was only part of the required work? Or should I completely ignore its content? One more thing, if I may: some changes were made to the modules _pom.xml_. Most of the time was about the _Embed-Dependency_ of the _maven-bundle-plugin_. That I find it hard to understand, and I feel it goes beyond my current knowledge of the code. > 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.3.4#803005)
[jira] [Comment Edited] (OAK-8967) OR query with ORDER BY don't work as expected
[ https://issues.apache.org/jira/browse/OAK-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432220#comment-17432220 ] Mohit Kataria edited comment on OAK-8967 at 10/21/21, 12:35 PM: Backported to 1.8 branch [https://github.com/apache/jackrabbit-oak/commit/4f840d1f3bf857b1b67430358cb6d7c7867388b6] was (Author: mkataria): Removing label : [candidate_oak_1_8|https://issues.apache.org/jira/issues/?jql=labels+%3D+candidate_oak_1_8] Will backport if some one asks for this. > OR query with ORDER BY don't work as expected > -- > > Key: OAK-8967 > URL: https://issues.apache.org/jira/browse/OAK-8967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing, search >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Fix For: 1.22.3, 1.30.0, 1.8.25 > > > A query with Or and having order by along with limit Don't reproduce results > as per order mentioned. > e.g. > Let content be: > "/UnionQueryTest1/node0", > "/UnionQueryTest/node0", > "/UnionQueryTest1/node0/node1", > "/UnionQueryTest/node0/node1", > "/UnionQueryTest1/node0/node1/node2", > "/UnionQueryTest/node0/node1/node2", > "/UnionQueryTest1/node0/node1/node2/node3", > "/UnionQueryTest/node0/node1/node2/node3" > each node having x = number in node name. > SELECT idn1.* FROM [nt:base] as idn1 WHERE > ISDESCENDANTNODE([/UnionQueryTest]) OR ISDESCENDANTNODE([/UnionQueryTest1]) > ORDER BY idn1.[x] ASC > > result should be same as above mentioned where as current result come out to > be > /UnionQueryTest1/node0 > /UnionQueryTest1/node0/node1 > /UnionQueryTest1/node0/node1/node2 > /UnionQueryTest1/node0/node1/node2/node3 > /UnionQueryTest1/node0/node1/node2/node3/node4 > /UnionQueryTest/node0 > /UnionQueryTest/node0/node1 > /UnionQueryTest/node0/node1/node2 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-8967) OR query with ORDER BY don't work as expected
[ https://issues.apache.org/jira/browse/OAK-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-8967: --- Fix Version/s: 1.8.25 > OR query with ORDER BY don't work as expected > -- > > Key: OAK-8967 > URL: https://issues.apache.org/jira/browse/OAK-8967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing, search >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Fix For: 1.22.3, 1.30.0, 1.8.25 > > > A query with Or and having order by along with limit Don't reproduce results > as per order mentioned. > e.g. > Let content be: > "/UnionQueryTest1/node0", > "/UnionQueryTest/node0", > "/UnionQueryTest1/node0/node1", > "/UnionQueryTest/node0/node1", > "/UnionQueryTest1/node0/node1/node2", > "/UnionQueryTest/node0/node1/node2", > "/UnionQueryTest1/node0/node1/node2/node3", > "/UnionQueryTest/node0/node1/node2/node3" > each node having x = number in node name. > SELECT idn1.* FROM [nt:base] as idn1 WHERE > ISDESCENDANTNODE([/UnionQueryTest]) OR ISDESCENDANTNODE([/UnionQueryTest1]) > ORDER BY idn1.[x] ASC > > result should be same as above mentioned where as current result come out to > be > /UnionQueryTest1/node0 > /UnionQueryTest1/node0/node1 > /UnionQueryTest1/node0/node1/node2 > /UnionQueryTest1/node0/node1/node2/node3 > /UnionQueryTest1/node0/node1/node2/node3/node4 > /UnionQueryTest/node0 > /UnionQueryTest/node0/node1 > /UnionQueryTest/node0/node1/node2 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OAK-9559) Migrate previously synced users/groups to dynamic membership
[ https://issues.apache.org/jira/browse/OAK-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber reassigned OAK-9559: - Assignee: Angela Schreiber > Migrate previously synced users/groups to dynamic membership > > > Key: OAK-9559 > URL: https://issues.apache.org/jira/browse/OAK-9559 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: auth-external >Reporter: Angela Schreiber >Assignee: Angela Schreiber >Priority: Major > > if configuration option _PARAM_USER_DYNAMIC_MEMBERSHIP_DEFAULT_ is enabled, > any external identities that have been synchronized before will fall back to > the original default sync behavior. > in order to provide consistent behavior for all synchronized users, > _oak-auth-external_ should provide some option to either migrate previously > synchronized identities or force a re-sync to establish dynamic membership > (and removed previously synced external groups). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-7208) Various disallowed control characters are accepted in item names
[ https://issues.apache.org/jira/browse/OAK-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7208: Labels: (was: candidate_oak_1_8) > Various disallowed control characters are accepted in item names > > > Key: OAK-7208 > URL: https://issues.apache.org/jira/browse/OAK-7208 > Project: Jackrabbit Oak > Issue Type: Bug > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.9.0, 1.10.0 > > Attachments: OAK-7208.diff > > > Our node name check currently allow control characters other than CR, LF and > TAB. This is a bug according to JCR, names being restricted to XML characters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OAK-9602) Script to check for inconsistent version nodes and generate a report
José Andrés Cordero Benítez created OAK-9602: Summary: Script to check for inconsistent version nodes and generate a report Key: OAK-9602 URL: https://issues.apache.org/jira/browse/OAK-9602 Project: Jackrabbit Oak Issue Type: New Feature Components: documentmk Reporter: José Andrés Cordero Benítez We have detected some external tools can introduce some changes in the version history nodes, leaving it inconsistent. The main problems we detected were: * Some version nodes are left empty, instead of removing the node completely. Leaving empty nodes that will trigger ConstraintViolations when they are traversed. * The primaryType of the node is changed incorrectly from nt:versionHistory to nt:version. I have created a script to traverse the versionHistory and detect if the NodeStore is affected by this issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-8044) AccessControlManagerImpl.getEffectivePolicies returns empty ACLs
[
https://issues.apache.org/jira/browse/OAK-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angela Schreiber updated OAK-8044:
--
Labels: (was: candidate_oak_1_8)
> AccessControlManagerImpl.getEffectivePolicies returns empty ACLs
>
>
> Key: OAK-8044
> URL: https://issues.apache.org/jira/browse/OAK-8044
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Minor
> Fix For: 1.12.0
>
>
> while writing tests for OAK-8000 i noticed that
> {{AccessControlManagerImpl.getEffectivePolicies}} may return empty access
> control lists. this doesn't seem valuable to me as they have no real effect.
> since i am indecided about OAK-8000 i would suggest to fix that separately.
> [~stillalex], fyi
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OAK-8023) AccessControlManagerImpl can not handle repository level when editing policies by principal
[
https://issues.apache.org/jira/browse/OAK-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angela Schreiber updated OAK-8023:
--
Labels: (was: candidate_oak_1_8)
> AccessControlManagerImpl can not handle repository level when editing
> policies by principal
> ---
>
> Key: OAK-8023
> URL: https://issues.apache.org/jira/browse/OAK-8023
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Minor
> Fix For: 1.12.0, 1.10.1
>
> Attachments: OAK-8023-2.patch, OAK-8023-3.patch, OAK-8023.patch
>
>
> [~stillalex], it seems that editing access control by principal in the
> default implementation doesn't allow for applying entries to the 'null' path.
> initially i thought that we can use an empty string value instead for the
> {{rep:nodePath}}, but that doesn't work as it gets converted to "." for some
> reason.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OAK-8967) OR query with ORDER BY don't work as expected
[ https://issues.apache.org/jira/browse/OAK-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-8967: --- Component/s: indexing > OR query with ORDER BY don't work as expected > -- > > Key: OAK-8967 > URL: https://issues.apache.org/jira/browse/OAK-8967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing, search >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Fix For: 1.22.3, 1.30.0 > > > A query with Or and having order by along with limit Don't reproduce results > as per order mentioned. > e.g. > Let content be: > "/UnionQueryTest1/node0", > "/UnionQueryTest/node0", > "/UnionQueryTest1/node0/node1", > "/UnionQueryTest/node0/node1", > "/UnionQueryTest1/node0/node1/node2", > "/UnionQueryTest/node0/node1/node2", > "/UnionQueryTest1/node0/node1/node2/node3", > "/UnionQueryTest/node0/node1/node2/node3" > each node having x = number in node name. > SELECT idn1.* FROM [nt:base] as idn1 WHERE > ISDESCENDANTNODE([/UnionQueryTest]) OR ISDESCENDANTNODE([/UnionQueryTest1]) > ORDER BY idn1.[x] ASC > > result should be same as above mentioned where as current result come out to > be > /UnionQueryTest1/node0 > /UnionQueryTest1/node0/node1 > /UnionQueryTest1/node0/node1/node2 > /UnionQueryTest1/node0/node1/node2/node3 > /UnionQueryTest1/node0/node1/node2/node3/node4 > /UnionQueryTest/node0 > /UnionQueryTest/node0/node1 > /UnionQueryTest/node0/node1/node2 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-8967) OR query with ORDER BY don't work as expected
[ https://issues.apache.org/jira/browse/OAK-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria updated OAK-8967: --- Labels: (was: candidate_oak_1_8) > OR query with ORDER BY don't work as expected > -- > > Key: OAK-8967 > URL: https://issues.apache.org/jira/browse/OAK-8967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: search >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Fix For: 1.22.3, 1.30.0 > > > A query with Or and having order by along with limit Don't reproduce results > as per order mentioned. > e.g. > Let content be: > "/UnionQueryTest1/node0", > "/UnionQueryTest/node0", > "/UnionQueryTest1/node0/node1", > "/UnionQueryTest/node0/node1", > "/UnionQueryTest1/node0/node1/node2", > "/UnionQueryTest/node0/node1/node2", > "/UnionQueryTest1/node0/node1/node2/node3", > "/UnionQueryTest/node0/node1/node2/node3" > each node having x = number in node name. > SELECT idn1.* FROM [nt:base] as idn1 WHERE > ISDESCENDANTNODE([/UnionQueryTest]) OR ISDESCENDANTNODE([/UnionQueryTest1]) > ORDER BY idn1.[x] ASC > > result should be same as above mentioned where as current result come out to > be > /UnionQueryTest1/node0 > /UnionQueryTest1/node0/node1 > /UnionQueryTest1/node0/node1/node2 > /UnionQueryTest1/node0/node1/node2/node3 > /UnionQueryTest1/node0/node1/node2/node3/node4 > /UnionQueryTest/node0 > /UnionQueryTest/node0/node1 > /UnionQueryTest/node0/node1/node2 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-8967) OR query with ORDER BY don't work as expected
[ https://issues.apache.org/jira/browse/OAK-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432220#comment-17432220 ] Mohit Kataria commented on OAK-8967: Removing label : [candidate_oak_1_8|https://issues.apache.org/jira/issues/?jql=labels+%3D+candidate_oak_1_8] Will backport if some one asks for this. > OR query with ORDER BY don't work as expected > -- > > Key: OAK-8967 > URL: https://issues.apache.org/jira/browse/OAK-8967 > Project: Jackrabbit Oak > Issue Type: Bug > Components: search >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > Labels: candidate_oak_1_8 > Fix For: 1.22.3, 1.30.0 > > > A query with Or and having order by along with limit Don't reproduce results > as per order mentioned. > e.g. > Let content be: > "/UnionQueryTest1/node0", > "/UnionQueryTest/node0", > "/UnionQueryTest1/node0/node1", > "/UnionQueryTest/node0/node1", > "/UnionQueryTest1/node0/node1/node2", > "/UnionQueryTest/node0/node1/node2", > "/UnionQueryTest1/node0/node1/node2/node3", > "/UnionQueryTest/node0/node1/node2/node3" > each node having x = number in node name. > SELECT idn1.* FROM [nt:base] as idn1 WHERE > ISDESCENDANTNODE([/UnionQueryTest]) OR ISDESCENDANTNODE([/UnionQueryTest1]) > ORDER BY idn1.[x] ASC > > result should be same as above mentioned where as current result come out to > be > /UnionQueryTest1/node0 > /UnionQueryTest1/node0/node1 > /UnionQueryTest1/node0/node1/node2 > /UnionQueryTest1/node0/node1/node2/node3 > /UnionQueryTest1/node0/node1/node2/node3/node4 > /UnionQueryTest/node0 > /UnionQueryTest/node0/node1 > /UnionQueryTest/node0/node1/node2 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
