[jira] [Created] (OAK-2034) Update parent pom.xml to latest 2.9 release
angela created OAK-2034: --- Summary: Update parent pom.xml to latest 2.9 release Key: OAK-2034 URL: https://issues.apache.org/jira/browse/OAK-2034 Project: Jackrabbit Oak Issue Type: Task Components: parent Reporter: angela Fix For: 1.1 in order to be able to commit the implementation of the API extensions made for JCR-3802 i had to set the jackrabbit version to 2.9-SNAPSHOT. in order to not keep us with a snapshot dependency for a longer while it would be good to update the pom.xml again once we make the next 2.9 release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OAK-1844) Verify resilience goals
[ https://issues.apache.org/jira/browse/OAK-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14098381#comment-14098381 ] Michael Dürig commented on OAK-1844: See the Article [The Network is Reliable | http://queue.acm.org/detail.cfm?id=2655736] for an informal report about network reliability. [Raw data | https://github.com/aphyr/partitions-post] on GitHub. Verify resilience goals --- Key: OAK-1844 URL: https://issues.apache.org/jira/browse/OAK-1844 Project: Jackrabbit Oak Issue Type: Task Reporter: Michael Dürig Assignee: Michael Dürig Labels: resilience Fix For: 1.1 This is a container issue for verifying the resilience goals set out for Oak. See https://wiki.apache.org/jackrabbit/Resilience for the work in progress of such goals. Once we have an agreement on that, subtasks of this issue could be used to track the verification process of each of the individual goals. Discussion here: http://jackrabbit.markmail.org/thread/5cndir5sjrc5dtla -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (OAK-2030) Remove ContentRepositoryImpl#getNodeStore
[
https://issues.apache.org/jira/browse/OAK-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-2030.
Resolution: Fixed
Fixed at http://svn.apache.org/r1618127
Remove ContentRepositoryImpl#getNodeStore
-
Key: OAK-2030
URL: https://issues.apache.org/jira/browse/OAK-2030
Project: Jackrabbit Oak
Issue Type: Improvement
Components: core
Reporter: Michael Dürig
Assignee: Michael Dürig
Fix For: 1.1
Attachments: OAK-2030.patch
{{ContentRepositoryImpl#getNodeStore}} was introduced with OAK-410 but latter
refactoring removed any dependencies again such that it is currently unused.
As the method breaks encapsulation I suggest we remove it again.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (OAK-1978) Add path exclusion to JackrabbitEventFilter
[ https://issues.apache.org/jira/browse/OAK-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig resolved OAK-1978. Resolution: Fixed Fix Version/s: 1.1 Fixed at http://svn.apache.org/r1618147 Add path exclusion to JackrabbitEventFilter --- Key: OAK-1978 URL: https://issues.apache.org/jira/browse/OAK-1978 Project: Jackrabbit Oak Issue Type: New Feature Components: core, jcr Reporter: Michael Dürig Assignee: Michael Dürig Labels: observation Fix For: 1.1 Implement the new Jackrabbit API introduced with JCR-3797 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (OAK-2026) Incompatibility with PropertyDefinitionImpl#getValueConstraints potentially returning null values.
[
https://issues.apache.org/jira/browse/OAK-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-2026.
Resolution: Fixed
Fix Version/s: 1.1
Assignee: Michael Dürig
Thanks Amit for the patch. Applied at http://svn.apache.org/r1618158
Incompatibility with PropertyDefinitionImpl#getValueConstraints potentially
returning null values.
--
Key: OAK-2026
URL: https://issues.apache.org/jira/browse/OAK-2026
Project: Jackrabbit Oak
Issue Type: Bug
Components: core
Reporter: Amit Jain
Assignee: Michael Dürig
Priority: Minor
Fix For: 1.1
Attachments: OAK-2026.patch
There is an compatibility issue with the
{{org.apache.jackrabbit.oak.plugins.nodetype.PropertyDefinitionImpl#getValueConstraints}}
where it returns null if not available.
In
{{org.apache.jackrabbit.webdav.jcr.nodetype.PropertyDefinitionImpl#toXml}}
call in the component {{jackrabbit-jcr-server}}, it assumes that
{{#getValueConstraints}} would not return null, which used to work with
Jackrabbit 2.x. But with Oak’s
{{org.apache.jackrabbit.oak.plugins.nodetype.AbstractTypeDefinition}}, where
the above call is delegated it can return null.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (OAK-2035) OrderedIndex fails to keep a correct skipList on TarMK
Davide Giannella created OAK-2035: - Summary: OrderedIndex fails to keep a correct skipList on TarMK Key: OAK-2035 URL: https://issues.apache.org/jira/browse/OAK-2035 Project: Jackrabbit Oak Issue Type: Bug Components: core, query Affects Versions: 1.0.4, 1.1 Reporter: Davide Giannella Assignee: Davide Giannella Priority: Critical When running on TarMK and pushing several dates into an ordered index, it happens that once in while it fails in seeking an already existing element and therefore interrupt the list the last added element. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (OAK-2035) OrderedIndex fails to keep a correct skipList on TarMK
[ https://issues.apache.org/jira/browse/OAK-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2035: -- Attachment: OrderedIndexIT.java Attaching [^OrderedIndexIT.java] with an integration testing for reproducing the scenario. OrderedIndex fails to keep a correct skipList on TarMK -- Key: OAK-2035 URL: https://issues.apache.org/jira/browse/OAK-2035 Project: Jackrabbit Oak Issue Type: Bug Components: core, query Affects Versions: 1.1, 1.0.4 Reporter: Davide Giannella Assignee: Davide Giannella Priority: Critical Attachments: OrderedIndexIT.java When running on TarMK and pushing several dates into an ordered index, it happens that once in while it fails in seeking an already existing element and therefore interrupt the list the last added element. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (OAK-2036) getPlan() output for NodeTypeIndex doesn't indicate the index type used
Justin Edelson created OAK-2036:
---
Summary: getPlan() output for NodeTypeIndex doesn't indicate the
index type used
Key: OAK-2036
URL: https://issues.apache.org/jira/browse/OAK-2036
Project: Jackrabbit Oak
Issue Type: Bug
Reporter: Justin Edelson
Fix For: 1.1
NodeTypeIndex's getPlan() method simply does this:
{code}
return filter.toString();
{code}
whereas all the other index implementation output their name. This should be
changed to, at minimum:
{code}
return nodetype + filter.toString();
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (OAK-2037) Define standards for plan output
Justin Edelson created OAK-2037: --- Summary: Define standards for plan output Key: OAK-2037 URL: https://issues.apache.org/jira/browse/OAK-2037 Project: Jackrabbit Oak Issue Type: Task Components: query Reporter: Justin Edelson Currently, the syntax for the plan output is chaotic as it varies significantly from index to index. Whereas some of this is expected - each index type will have different data to output, Oak should provide some standards about how a plan will appear. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OAK-1996) let 'order by @jcr:score' trigger automatic result set size calculation
[ https://issues.apache.org/jira/browse/OAK-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099497#comment-14099497 ] Torgeir Veimo commented on OAK-1996: Maybe there could be a flag to set at repository init that triggered better compatibility with jackrabbit apps? let 'order by @jcr:score' trigger automatic result set size calculation --- Key: OAK-1996 URL: https://issues.apache.org/jira/browse/OAK-1996 Project: Jackrabbit Oak Issue Type: Improvement Components: query Affects Versions: 1.0.3 Reporter: Torgeir Veimo It would probably be a good idea to make the order by @jcr:score suffix trigger automatic result set size calculation in getSize() for better backwards compatibility. This would make oak more compatible with applications relying on this behaviour from jackrabbit 2.8 and earlier. -- This message was sent by Atlassian JIRA (v6.2#6252)
