[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198200#comment-16198200 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #853|https://builds.apache.org/job/Jackrabbit%20Oak/853/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/853/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198195#comment-16198195
]
Chetan Mehrotra commented on OAK-6790:
--
bq. I'm guessing consumer of this class would have to mark dependency on
oak-query-spi anyway
Not necessarily as his code would still compile fine with older maven
dependency however his existing working app would not work post upgrade as his
bundle using the older FacetResult would not resolve
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.10
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198191#comment-16198191
]
Vikas Saurabh commented on OAK-6790:
[~chetanm], I'm guessing consumer of this class would have to mark dependency
on {{oak-query-spi}} anyway. So, unless we move it back to {{oak-core}}, I am
not sure if not changing package would be helpful from backward compatibility
pov.
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.10
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6763) Convert oak-examples to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved OAK-6763. -- Resolution: Fixed Assignee: Chetan Mehrotra > Convert oak-examples to OSGi R6 annotations > --- > > Key: OAK-6763 > URL: https://issues.apache.org/jira/browse/OAK-6763 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Robert Munteanu >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6763) Convert oak-examples to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198160#comment-16198160 ] Chetan Mehrotra commented on OAK-6763: -- Modules under examples are not OSGi bundles. There was a unused dependency on Felix SCR Annotation in oak-standalone. Removed that with r1811637 > Convert oak-examples to OSGi R6 annotations > --- > > Key: OAK-6763 > URL: https://issues.apache.org/jira/browse/OAK-6763 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6803) Provide a way to for persistent cache to determine which all nodes can be cached
[ https://issues.apache.org/jira/browse/OAK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6803: - Summary: Provide a way to for persistent cache to determine which all nodes can be cached (was: Provide a way to for persistent cache to determine which all nodes are cached) > Provide a way to for persistent cache to determine which all nodes can be > cached > > > Key: OAK-6803 > URL: https://issues.apache.org/jira/browse/OAK-6803 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8 > > Attachments: OAK-6803-v1.patch > > > Currently persistent cache if enabled for nodes caches all nodes accessed on > the system. It would be better if it can be configured to only cache those > nodes which are not volatile so that caching can be effective > Purpose of this issue is to > * Provide an extension point in PersistentCache logic to check if a node is > to be cached > * Provide an impl which relies on some static OSGi config to determine that > Later we can make this impl dynamic i.e. rely on access pattern to cache imp > stuff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198153#comment-16198153
]
Chetan Mehrotra commented on OAK-6790:
--
[~catholicon] If the package is not used in multiple bundles
"org.apache.jackrabbit.oak.query.facet" then lets keep the same package name to
avoid any backward compatibility issue as this class was sort of api
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.10
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197924#comment-16197924 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #852|https://builds.apache.org/job/Jackrabbit%20Oak/852/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/852/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh resolved OAK-6790.
Resolution: Fixed
Fix Version/s: 1.7.10
Re-exported the class under {{oak-query-spi}} under {{o.a.j.o.spi.query.facet}}
on trunk at [r1811626|https://svn.apache.org/r1811626].
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.10
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197848#comment-16197848 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #851|https://builds.apache.org/job/Jackrabbit%20Oak/851/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/851/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197773#comment-16197773 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #850|https://builds.apache.org/job/Jackrabbit%20Oak/850/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/850/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6757) Convert oak-auth-ldap to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6757: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-auth-ldap to OSGi R6 annotations > > > Key: OAK-6757 > URL: https://issues.apache.org/jira/browse/OAK-6757 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-ldap >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5998) Clarify and complete missing stuff in current Oak documentation
[ https://issues.apache.org/jira/browse/OAK-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5998: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Clarify and complete missing stuff in current Oak documentation > --- > > Key: OAK-5998 > URL: https://issues.apache.org/jira/browse/OAK-5998 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.10 > > > Current Oak documentation [1] is missing details around certain aspects of > Oak which makes it difficult for a new person to get up and running and more > important operate Oak in productions easily. Purpose of this task is list out > topic which must be documented to enable easier usage of Oak > * Getting Started - Getting Oak with all features properly is tricky and not > easily possible with our [current getting > started|https://jackrabbit.apache.org/oak/docs/construct.html] specially for > prod setup. > ** Possibly refer or move doc of current examples here > ** For a new user not aware of JCR but aware of document storage a brief > overview on the JCR and how its the api for Oak which is to be used > * Maintenance and Operations - > ** Oak being MVCC storage requires certain maintenance task like RevisionGC > and BlobGC to be run periodically. > ** Then related MBean should be documented. Note some part is covered in > [Segment > docs|https://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#garbage-collection] > but we need to complete it for Document and also provide an overview > ** System requirements in terms of RAM due to memory mapped usage, cloned > index files and persistent cache > * How clustering works in Oak - [Clustering > doc|https://jackrabbit.apache.org/oak/docs/clustering.html] should provide > details on > ** how it works > ** importance of background read and background write > ** Effect of eventual consistency in cluster setup > ** Sticky session requirement (as per usecase) > * Observation > ** How it works > ** How external and local events are generated > ** Queue behaviour and overflow > * Clarify requirement from host application wrt > ** scheduling singleton jobs used in Oak and how they should be executed > ** Scheduling maintenance operations via MBeans > * Document various OSGi config - May be generate a doc for all OSGi config in > Oak via some tooling > Note list above is tentative and would be edited to determine important > topics in coming days and then specific sub task can be created to complete > it. Once any list item is completed add (/) against the list entry > [1] https://jackrabbit.apache.org/oak/docs/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5763) Improve LockException message on org.apache.jackrabbit.oak.jcr.lock.LockManagerImpl unlock
[
https://issues.apache.org/jira/browse/OAK-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5763:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Improve LockException message on
> org.apache.jackrabbit.oak.jcr.lock.LockManagerImpl unlock
> --
>
> Key: OAK-5763
> URL: https://issues.apache.org/jira/browse/OAK-5763
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
>Affects Versions: 1.3.3
>Reporter: Borja Clemente
> Fix For: 1.8, 1.7.10
>
>
> The error message on LockManagerImpl unlock method could also include
> information about the user attempting to unlock the node as well as the
> actual lock owner.
> Current exception is:
> {code}
> LockException("Not an owner of the lock " + path)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6770: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-segment-tar to OSGi R6 annotations > -- > > Key: OAK-6770 > URL: https://issues.apache.org/jira/browse/OAK-6770 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5455:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.10
>
> Attachments: OAK-5455-v1.patch, enforce.diff
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5963) Disable S3 proactive caching by default
[ https://issues.apache.org/jira/browse/OAK-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5963: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Disable S3 proactive caching by default > --- > > Key: OAK-5963 > URL: https://issues.apache.org/jira/browse/OAK-5963 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Labels: candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6 > Fix For: 1.8, 1.7.10 > > > The older JR2 CachingDataStore which is extended by S3DataStore enables > proactive caching by default which leads to many binaries being downloaded > twice. This should be disabled by default in Oak. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6759) Convert oak-blob-cloud-azure to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6759: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-blob-cloud-azure to OSGi R6 annotations > --- > > Key: OAK-6759 > URL: https://issues.apache.org/jira/browse/OAK-6759 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-cloud >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6769) Convert oak-search-mt to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6769: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-search-mt to OSGi R6 annotations > > > Key: OAK-6769 > URL: https://issues.apache.org/jira/browse/OAK-6769 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6768) Convert oak-remote to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6768: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-remote to OSGi R6 annotations > - > > Key: OAK-6768 > URL: https://issues.apache.org/jira/browse/OAK-6768 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: remoting >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6580) Ensure mounts are consistent with the node type registry
[ https://issues.apache.org/jira/browse/OAK-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6580: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Ensure mounts are consistent with the node type registry > > > Key: OAK-6580 > URL: https://issues.apache.org/jira/browse/OAK-6580 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >Reporter: Robert Munteanu >Assignee: Robert Munteanu > Fix For: 1.8, 1.7.10 > > Attachments: > 0001-OAK-6580-Ensure-mounts-are-consistent-with-the-node-.patch > > > When a mount is added, we should make sure that the nodes are: > * defined in the NodeTypeRegistry > * consistent with the node type definitions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5635) Revisit FileStoreStats mbean stats format
[ https://issues.apache.org/jira/browse/OAK-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5635: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Revisit FileStoreStats mbean stats format > - > > Key: OAK-5635 > URL: https://issues.apache.org/jira/browse/OAK-5635 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Alex Deparvu >Assignee: Michael Dürig > Labels: monitoring > Fix For: 1.8, 1.7.10 > > > This is a bigger refactoring item to revisit the format of the exposed data, > moving towards having it in a more machine consumable friendly format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6674) Create a more complex IT for cold standby
[
https://issues.apache.org/jira/browse/OAK-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6674:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Create a more complex IT for cold standby
> -
>
> Key: OAK-6674
> URL: https://issues.apache.org/jira/browse/OAK-6674
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
> Labels: cold-standby
> Fix For: 1.8, 1.7.10
>
>
> At the moment all integration tests for cold standby are using the same
> scenario in their tests: some content is created on the server (including
> binaries), a standby sync cycle is started and then the content is checked on
> the client. The only twist here is using/not using a data store for storing
> binaries.
> Although good, this model could be extended to cover many more cases. For
> example, {{StandbyDiff}} covers the following 6 cases node/property
> added/changed/deleted. From these, with the scenario described, the removal
> part is never tested (and the change part is covered in only one test).
> It would be nice to have an IT which would add content on the server, do a
> sync, remove some of the content, do a sync and then call OnRC. This way all
> cases will be covered, including if cleanup works as expected on the client.
> /cc [~frm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6766) Convert oak-lucene to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6766: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-lucene to OSGi R6 annotations > - > > Key: OAK-6766 > URL: https://issues.apache.org/jira/browse/OAK-6766 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6711) Refactor IndexConstants so it can be referenced from outside oak-core
[ https://issues.apache.org/jira/browse/OAK-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6711: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Refactor IndexConstants so it can be referenced from outside oak-core > - > > Key: OAK-6711 > URL: https://issues.apache.org/jira/browse/OAK-6711 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: core >Reporter: Alex Deparvu >Assignee: Alex Deparvu > Fix For: 1.8, 1.7.10 > > > This is blocking OAK-6318, the security spi code depends on this constants > class so I'd like to move it to a different location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5975) Document enhancements in Observation in 1.6
[ https://issues.apache.org/jira/browse/OAK-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5975: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Document enhancements in Observation in 1.6 > --- > > Key: OAK-5975 > URL: https://issues.apache.org/jira/browse/OAK-5975 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.10 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs wrt JCR Observation area > * OAK-4796 - filter events before adding to ChangeProcessor's queue > * OAK-5020 - Improved support for node removals > * OAK-5021 - Improve observation of files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6765) Convert oak-jcr to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6765: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-jcr to OSGi R6 annotations > -- > > Key: OAK-6765 > URL: https://issues.apache.org/jira/browse/OAK-6765 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6767) Remove felix SCR annotation support from parent pom
[ https://issues.apache.org/jira/browse/OAK-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6767: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Remove felix SCR annotation support from parent pom > --- > > Key: OAK-6767 > URL: https://issues.apache.org/jira/browse/OAK-6767 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6615) Add new segment-tar fixture for attaching a cold-standby to benchmarked primary
[
https://issues.apache.org/jira/browse/OAK-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6615:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Add new segment-tar fixture for attaching a cold-standby to benchmarked
> primary
> ---
>
> Key: OAK-6615
> URL: https://issues.apache.org/jira/browse/OAK-6615
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: benchmarks, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.10
>
>
> If this fixture is chosen, a cold standby instance will be started, syncing
> with the primary every {{n}} seconds. All the benchmarks specified via
> {{[testcases]}} argument will be run on primary instance, and all statistics
> and reports will be linked to primary.
> This could work similarly to {{Oak-Segment-Tar-DS}} and have dedicated
> options like {{--no-data-store}}, {{--private-data-store}} or
> {{--shared-data-store}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5546) [BlobGC] Adapt time to delete blobs based on lucene indexing activity
[
https://issues.apache.org/jira/browse/OAK-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5546:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> [BlobGC] Adapt time to delete blobs based on lucene indexing activity
> -
>
> Key: OAK-5546
> URL: https://issues.apache.org/jira/browse/OAK-5546
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.10
>
>
> Blob GC deletes only those candidate blobs which are older from current than
> the configured {{blobGcMaxAgeInSecs}} interval (Default to 24 hours).
> This should be improved to take into time long running lucene re-indexing
> task which can potentially run into days for large repositories as otherwise
> it risks data loss and index corruption.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5877) Oak upgrade usage note refers to oak-run
[
https://issues.apache.org/jira/browse/OAK-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5877:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Oak upgrade usage note refers to oak-run
>
>
> Key: OAK-5877
> URL: https://issues.apache.org/jira/browse/OAK-5877
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: Michael Dürig
>Priority: Minor
> Labels: production, tooling, usability
> Fix For: 1.8, 1.7.10
>
>
> Running {{java -jar oak-upgrade*.jar}} prints
> {noformat}
> Usage: java -jar oak-run-*-jr2.jar upgrade [options] jcr2_source [destination]
>(to upgrade a JCR 2 repository)
>java -jar oak-run-*-jr2.jar upgrade [options] source destination
>(to migrate an Oak repository)
> {noformat}
> Which incorrectly refers to {{oak-run upgrade}}. The latter will send me back
> to {{oak-run}}: "This command was moved to the oak-upgrade module".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6737) Standby server should send timely responses to all client requests
[
https://issues.apache.org/jira/browse/OAK-6737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6737:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Standby server should send timely responses to all client requests
> --
>
> Key: OAK-6737
> URL: https://issues.apache.org/jira/browse/OAK-6737
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.10
>
>
> Currently all the {{GetXXXRequestHandler}} (where XXX stands for Blob, Head,
> References and Segment), on the server discard client requests which cannot
> be satisfied (i.e. the requested object does not exist (yet) on the server).
> A more transparent approach would be to timely respond to all client
> requests, clearly stating that the object was not found. This would improve a
> lot debugging for example, because all requests and their responses could be
> easily followed from the client log, without needing to know what actually
> happened on the server.
> Below, a possible implementation for {{GetHeadRequestHandler}}, suggested by
> [~frm] in a comment on OAK-6678:
> {noformat}
> String id = reader.readHeadRecordId();
> if (id == null) {
> ctx.writeAndFlush(new NotFoundGetHeadResponse(msg.getClientId(), id));
> return;
> }
> ctx.writeAndFlush(new GetHeadResponse(msg.getClientId(), id));
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6774) Convert oak-upgrade to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6774: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-upgrade to OSGi R6 annotations > -- > > Key: OAK-6774 > URL: https://issues.apache.org/jira/browse/OAK-6774 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: upgrade >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6606) Move BulkTransferBenchmark to oak-benchmarks module
[
https://issues.apache.org/jira/browse/OAK-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6606:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Move BulkTransferBenchmark to oak-benchmarks module
> ---
>
> Key: OAK-6606
> URL: https://issues.apache.org/jira/browse/OAK-6606
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.10
>
>
> {{BulkTransferBenchmark}} should be moved from {{oak-segment-tar}} to
> {{oak-benchmarks}} to allow standard run of this cold standby related
> benchmark.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6575) Provide a secure external URL to a DataStore binary.
[
https://issues.apache.org/jira/browse/OAK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6575:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Provide a secure external URL to a DataStore binary.
>
>
> Key: OAK-6575
> URL: https://issues.apache.org/jira/browse/OAK-6575
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: blob, core, jcr, security
>Reporter: Ian Boston
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.10
>
>
> Where the DataStore is a DataStore that may be accessed over an independent
> API it would be advantageous for Oak to provide a secure URL to allow direct,
> read only access to the current immutable instance of that binary. The term
> "secure" needs to be defined, but typically it would a URL that is valid for
> a appropriately short length of time to ensure that the risk of the URL being
> used by a user that it was not intended for, is minimised. It should also
> ensure that anyone in possession of the URL could not use the information in
> the url to create a valid URL or a valid URL to a different binary.
> One example of such a URL might be a AWS Signed URL as used by AWS CloudFront
> to access private content. The signed url being signed by a private key known
> only to the Oak instance and the the CloudFront or S3 instance. The signed
> url having a significantly low ttl so that a redirect by the same client
> would work.
> Oak should only emit these URLs to sessions that could otherwise read the
> binary directly from Oak, and Oak should be in complete control of the nature
> of the url and the security mechanisms applied to the URL.
> The viability of the approach has been investigated showing that given a JCR
> Binary it is possible to get the Oak Blob Content Identifier using
> ValueImpl.getBlob((Value)jcrBinary).getContentIentifier() and form there,
> knowing the way in which the DataStore implementation transforms that into a
> pointer into the datastore implementation form a URL to be made secure.
> To achieve the above, internal implementation details specific to the Oak
> DataStore implementation are required, hence this request to implement as a
> part of Oak rather than to reverse engineer in some external project.
> Since API changes are often significant using the Sling AdapaterFactory
> approach would allow a ServletFilter to selectively use the URL in a
> redirect, avoiding any new API methods to existing Oak APIs. A new interface
> might be required, in the example below that interface is SignedBinaryURL.
> {code}
> public void doFilter(ServletRequest servletRequest, ServletResponse
> servletResponse, FilterChain filterChain) throws IOException,
> ServletException {
> if ( servletRequest instanceof SlingHttpServletRequest &&
> servletResponse instanceof SlingHttpServletResponse) {
> if ("GET".equals(((SlingHttpServletRequest)
> servletRequest).getMethod())){
> Resource resource = ((SlingHttpServletRequest)
> servletRequest).getResource();
> SignedBinaryURL url = resource.adaptTo(SignedBinaryURL.class);
> if (url != null) {
> ((SlingHttpServletResponse)
> servletResponse).sendRedirect(url.getURL());
> return;
> }
> }
> }
> filterChain.doFilter(servletRequest, servletResponse);
> }
> {code}
> If the AdapterFactory to go from Binary to SingedBinaryURL is not present
> then url will always be null, and no-op. If it is present, and Oak decides no
> URL is appropriate, then no-op.
> Only if the Oak DS implementation being used supports the external URL and
> Oak decides it is appropriate, will a url be available and a redirect
> performed.
> I have used AWS S3 URLs as an example, however the approach should be
> applicable (and pluggable) to most REST based APIs to private binary content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6542) java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir
[ https://issues.apache.org/jira/browse/OAK-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6542: -- Fix Version/s: (was: 1.7.9) 1.7.10 > java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir > -- > > Key: OAK-6542 > URL: https://issues.apache.org/jira/browse/OAK-6542 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-tar >Affects Versions: 1.7.5 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Andrei Dulceanu > Fix For: 1.8, 1.7.10 > > > Upgrading to last 1.7.5. > I get this exception > java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore.(SegmentNodeStore.java:166) > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore.(SegmentNodeStore.java:63) > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore$SegmentNodeStoreBuilder.build(SegmentNodeStore.java:121) > Looking at the pom the dependency has a scope provided > (http://repo.maven.apache.org/maven2/org/apache/jackrabbit/oak-segment-tar/1.7.5/oak-segment-tar-1.7.5.pom) > IMHO it's a wrong dependency scope at it's definitely needed as there is no > usage of reflection to avoid loading of the classes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6760) Convert oak-blob-cloud to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6760: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-blob-cloud to OSGi R6 annotations > - > > Key: OAK-6760 > URL: https://issues.apache.org/jira/browse/OAK-6760 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-cloud >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6626) Replace standby blob chunk size configuration with feature flag
[
https://issues.apache.org/jira/browse/OAK-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6626:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Replace standby blob chunk size configuration with feature flag
> ---
>
> Key: OAK-6626
> URL: https://issues.apache.org/jira/browse/OAK-6626
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: cold-standby, configuration
> Fix For: 1.8, 1.7.10
>
>
> We should remove the {{StandbyStoreService#BLOB_CHUNK_SIZE}} OSGi
> configuration and replace it with a feature flag. Rational: we expect
> customer to rarely change this thus not justifying the additional
> configuration complexity and testing overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6761) Convert oak-blob-plugins to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6761: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-blob-plugins to OSGi R6 annotations > --- > > Key: OAK-6761 > URL: https://issues.apache.org/jira/browse/OAK-6761 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-plugins >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6594) UpgradeIT produces unwanted output
[
https://issues.apache.org/jira/browse/OAK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6594:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> UpgradeIT produces unwanted output
> --
>
> Key: OAK-6594
> URL: https://issues.apache.org/jira/browse/OAK-6594
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Michael Dürig
>Priority: Minor
> Fix For: 1.8, 1.7.10
>
>
> When {{UpgradeIT}} is executed, the following output is produced.
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> {
[jira] [Updated] (OAK-6763) Convert oak-examples to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6763: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-examples to OSGi R6 annotations > --- > > Key: OAK-6763 > URL: https://issues.apache.org/jira/browse/OAK-6763 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-4891) Mount-time sanity checks for mounted NodeStore instances
[ https://issues.apache.org/jira/browse/OAK-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-4891: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Mount-time sanity checks for mounted NodeStore instances > > > Key: OAK-4891 > URL: https://issues.apache.org/jira/browse/OAK-4891 > Project: Jackrabbit Oak > Issue Type: Task > Components: core >Reporter: Robert Munteanu >Assignee: Robert Munteanu > Fix For: 1.8, 1.7.10 > > > When mounting a NodeStore we should be able to run a quick sanity check to > make sure that it does not use any features which are troublesome, notably > those which would contribute to one of the 'global' states of Oak: > - versioned nodes > - referenceable nodes > - etc ( more TDB ) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5965) Support path exclusion in secondary nodestore
[ https://issues.apache.org/jira/browse/OAK-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5965: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Support path exclusion in secondary nodestore > - > > Key: OAK-5965 > URL: https://issues.apache.org/jira/browse/OAK-5965 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Labels: secondary-nodestore > Fix For: 1.8, 1.7.10 > > > Secondary NodeStore feature (OAK-4180) for now currently supports path > inclusion. It would be useful to have support for path exclusion also. > Using this a user can can include all content under / but exclude > /oak:index/uuid/:index entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6758) Convert oak-authorization-cug to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6758: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-authorization-cug to OSGi R6 annotations > > > Key: OAK-6758 > URL: https://issues.apache.org/jira/browse/OAK-6758 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: authorization-cug >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6773) Convert oak-store-composite to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6773: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-store-composite to OSGi R6 annotations > -- > > Key: OAK-6773 > URL: https://issues.apache.org/jira/browse/OAK-6773 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5360) Cancellation of gc should be reflected by RevisionGC.getRevisionGCStatus()
[
https://issues.apache.org/jira/browse/OAK-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5360:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Cancellation of gc should be reflected by RevisionGC.getRevisionGCStatus()
> --
>
> Key: OAK-5360
> URL: https://issues.apache.org/jira/browse/OAK-5360
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: gc, management, monitoring, production
> Fix For: 1.8, 1.7.10
>
>
> Currently when a garbage collection cycle is cancelled from "within" (i.e.
> through {{CancelCompactionSupplier}} then this is not reflected through
> {{RevisionGC.getRevisionGCStatus()}} but rather reported as successful run.
> We should change this and return a failure result indication the cancellation
> so downstream consumers get an proper indication whether and which gc runs
> actually succeeded.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6741: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R6 annotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization
[
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5521:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> CommunicationObserver and its MBeans need proper synchronization
>
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.10
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called
> concurrently by multiple threads. The implementation of
> {{CommunicationObserver}} doesn't currently use any form of synchronization
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As
> such, further synchronization is also needed in the MBeans to protect
> concurrent access to shared data.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6627) Backup restore should interact properly with older segment version
[ https://issues.apache.org/jira/browse/OAK-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6627: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Backup restore should interact properly with older segment version > -- > > Key: OAK-6627 > URL: https://issues.apache.org/jira/browse/OAK-6627 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Michael Dürig >Assignee: Michael Dürig > Labels: production, resilience > Fix For: 1.8, 1.7.10 > > > We need to check how backup and restore behave when run on top of a former > store version. That is backup / restore from Oak 1.8 to / from stores of > segment version 12 (from Oak 1.6). Expected behaviour is "nothing bad > happens". Details to be clarified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6756) Convert oak-auth-external to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6756: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-auth-external to OSGi R6 annotations > > > Key: OAK-6756 > URL: https://issues.apache.org/jira/browse/OAK-6756 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-external >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6764) Convert oak-exercise to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6764: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-exercise to OSGi R6 annotations > --- > > Key: OAK-6764 > URL: https://issues.apache.org/jira/browse/OAK-6764 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: exercise >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6762) Convert oak-blob to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6762: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Convert oak-blob to OSGi R6 annotations > --- > > Key: OAK-6762 > URL: https://issues.apache.org/jira/browse/OAK-6762 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5976) Document enhancements in 1.6 release
[ https://issues.apache.org/jira/browse/OAK-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5976: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Document enhancements in 1.6 release > > > Key: OAK-5976 > URL: https://issues.apache.org/jira/browse/OAK-5976 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.10 > > > We should document all the enhancement that have been done in Oak 1.6 release > and refer to them in main doc > * 1.6.0 Release Notes - > https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.6.0/RELEASE-NOTES.txt -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5918) Document enhancements in DocumentNodeStore in 1.6
[ https://issues.apache.org/jira/browse/OAK-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5918: -- Fix Version/s: (was: 1.7.9) 1.7.10 > Document enhancements in DocumentNodeStore in 1.6 > - > > Key: OAK-5918 > URL: https://issues.apache.org/jira/browse/OAK-5918 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.10 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs. Specially those enhancements which impact > system administration or new features which need be to enabled as per > requirements should be documented > Issues in documentmk, mongomk, rdbmk > [jql|https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.6.0%20and%20component%20in%20(documentmk%2C%20mongomk%2C%20rdbmk)%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC=200] > * OAK-1312 - Bundle nodes into a document (/) > * OAK-4180 - Use another NodeStore as a local cache for a remote Document > store (/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5896) fix typo in Not condition handling
[ https://issues.apache.org/jira/browse/OAK-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5896: -- Fix Version/s: (was: 1.7.9) 1.7.10 > fix typo in Not condition handling > -- > > Key: OAK-5896 > URL: https://issues.apache.org/jira/browse/OAK-5896 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 1.6.1 >Reporter: Dave Brosius >Assignee: Dave Brosius >Priority: Trivial > Fix For: 1.8, 1.7.10 > > Attachments: 5896.txt > > > code stutters the same condition twice, looks like a typo. patch attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5884) Evaluate utility of RepositoryGrowthTest benchmark
[
https://issues.apache.org/jira/browse/OAK-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5884:
--
Fix Version/s: (was: 1.7.9)
1.7.10
> Evaluate utility of RepositoryGrowthTest benchmark
> --
>
> Key: OAK-5884
> URL: https://issues.apache.org/jira/browse/OAK-5884
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: run
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Fix For: 1.8, 1.7.10
>
>
> {{RepositoryGrowthTest}} is a benchmark which makes use of the deprecated
> {{SegmentFixture}}. Since OAK-5834 removes the old {{oak-segment}} module and
> the code associated with it, {{RepositoryGrowthTest}} was also removed. If
> there's value in it, we can adapt it to work with the new
> {{SegmentTarFixture}}.
> /cc [~chetanm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6542) java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir
[ https://issues.apache.org/jira/browse/OAK-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6542: -- Fix Version/s: 1.8 > java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir > -- > > Key: OAK-6542 > URL: https://issues.apache.org/jira/browse/OAK-6542 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-tar >Affects Versions: 1.7.5 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Andrei Dulceanu > Fix For: 1.8, 1.7.9 > > > Upgrading to last 1.7.5. > I get this exception > java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore.(SegmentNodeStore.java:166) > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore.(SegmentNodeStore.java:63) > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore$SegmentNodeStoreBuilder.build(SegmentNodeStore.java:121) > Looking at the pom the dependency has a scope provided > (http://repo.maven.apache.org/maven2/org/apache/jackrabbit/oak-segment-tar/1.7.5/oak-segment-tar-1.7.5.pom) > IMHO it's a wrong dependency scope at it's definitely needed as there is no > usage of reflection to avoid loading of the classes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6674) Create a more complex IT for cold standby
[
https://issues.apache.org/jira/browse/OAK-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6674:
--
Fix Version/s: 1.8
> Create a more complex IT for cold standby
> -
>
> Key: OAK-6674
> URL: https://issues.apache.org/jira/browse/OAK-6674
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
> Labels: cold-standby
> Fix For: 1.8, 1.7.9
>
>
> At the moment all integration tests for cold standby are using the same
> scenario in their tests: some content is created on the server (including
> binaries), a standby sync cycle is started and then the content is checked on
> the client. The only twist here is using/not using a data store for storing
> binaries.
> Although good, this model could be extended to cover many more cases. For
> example, {{StandbyDiff}} covers the following 6 cases node/property
> added/changed/deleted. From these, with the scenario described, the removal
> part is never tested (and the change part is covered in only one test).
> It would be nice to have an IT which would add content on the server, do a
> sync, remove some of the content, do a sync and then call OnRC. This way all
> cases will be covered, including if cleanup works as expected on the client.
> /cc [~frm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6711) Refactor IndexConstants so it can be referenced from outside oak-core
[ https://issues.apache.org/jira/browse/OAK-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6711: -- Fix Version/s: 1.8 > Refactor IndexConstants so it can be referenced from outside oak-core > - > > Key: OAK-6711 > URL: https://issues.apache.org/jira/browse/OAK-6711 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: core >Reporter: Alex Deparvu >Assignee: Alex Deparvu > Fix For: 1.8, 1.7.9 > > > This is blocking OAK-6318, the security spi code depends on this constants > class so I'd like to move it to a different location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6650) new release checksum requirements
[ https://issues.apache.org/jira/browse/OAK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197626#comment-16197626 ] Davide Giannella commented on OAK-6650: --- [~reschke] bq. Is this what I was supposed to test? testing the full release cycle is rather difficult so we can really test only this bits. However a another pair of eyes on this few lines of patches could ease any future troubles. If the patches look good for you I will move this foreword so that you can apply the counterpart for jackrabbit. Otherwise the checkrelease script as modified now will fail for JR releases. > new release checksum requirements > - > > Key: OAK-6650 > URL: https://issues.apache.org/jira/browse/OAK-6650 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Davide Giannella >Assignee: Davide Giannella > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8 > > Attachments: OAK-6650-checkrelease.diff > > > As of various SHA algorithm the Apache policies around signatures and > checksums changed requiring to specify the sha algorithm as part of the file > extension: sha1, sha256, sha512. > http://www.apache.org/dev/release-distribution#sigs-and-sums > currently Oak signs with sha-1 and we should at least change the file > extension > h3. impacted areas > - release process (pom.xml) > - check release > - html download page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6803) Provide a way to for persistent cache to determine which all nodes are cached
[
https://issues.apache.org/jira/browse/OAK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-6803:
-
Attachment: OAK-6803-v1.patch
[patch|^OAK-6803-v1.patch] for the same.
It introduces a new OSGi config {{persistentCacheIncludes}} which can be used
to configure an array of paths which are (including there children) allowed to
be included in persistentCache. It defaults to "['/']"
[~tomek.rekawek] [~mreutegg] Please review
> Provide a way to for persistent cache to determine which all nodes are cached
> -
>
> Key: OAK-6803
> URL: https://issues.apache.org/jira/browse/OAK-6803
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Chetan Mehrotra
> Fix For: 1.8
>
> Attachments: OAK-6803-v1.patch
>
>
> Currently persistent cache if enabled for nodes caches all nodes accessed on
> the system. It would be better if it can be configured to only cache those
> nodes which are not volatile so that caching can be effective
> Purpose of this issue is to
> * Provide an extension point in PersistentCache logic to check if a node is
> to be cached
> * Provide an impl which relies on some static OSGi config to determine that
> Later we can make this impl dynamic i.e. rely on access pattern to cache imp
> stuff
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OAK-6803) Provide a way to for persistent cache to determine which all nodes are cached
[ https://issues.apache.org/jira/browse/OAK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra reassigned OAK-6803: Assignee: Chetan Mehrotra > Provide a way to for persistent cache to determine which all nodes are cached > - > > Key: OAK-6803 > URL: https://issues.apache.org/jira/browse/OAK-6803 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6803-v1.patch > > > Currently persistent cache if enabled for nodes caches all nodes accessed on > the system. It would be better if it can be configured to only cache those > nodes which are not volatile so that caching can be effective > Purpose of this issue is to > * Provide an extension point in PersistentCache logic to check if a node is > to be cached > * Provide an impl which relies on some static OSGi config to determine that > Later we can make this impl dynamic i.e. rely on access pattern to cache imp > stuff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6803) Provide a way to for persistent cache to determine which all nodes are cached
[ https://issues.apache.org/jira/browse/OAK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6803: - Priority: Minor (was: Major) > Provide a way to for persistent cache to determine which all nodes are cached > - > > Key: OAK-6803 > URL: https://issues.apache.org/jira/browse/OAK-6803 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8 > > Attachments: OAK-6803-v1.patch > > > Currently persistent cache if enabled for nodes caches all nodes accessed on > the system. It would be better if it can be configured to only cache those > nodes which are not volatile so that caching can be effective > Purpose of this issue is to > * Provide an extension point in PersistentCache logic to check if a node is > to be cached > * Provide an impl which relies on some static OSGi config to determine that > Later we can make this impl dynamic i.e. rely on access pattern to cache imp > stuff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197016#comment-16197016
]
Julian Reschke edited comment on OAK-6782 at 10/9/17 3:04 PM:
--
trunk: [r1811575|http://svn.apache.org/r1811575]
1.6: [r1811579|http://svn.apache.org/r1811579]
was (Author: reschke):
trunk: [r1811575|http://svn.apache.org/r1811575]
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.8, 1.7.9, 1.6.6
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6782:
Fix Version/s: 1.6.6
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.8, 1.7.9, 1.6.6
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6782:
Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 (was:
candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6)
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.8, 1.7.9, 1.6.6
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197119#comment-16197119 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #849|https://builds.apache.org/job/Jackrabbit%20Oak/849/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/849/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197016#comment-16197016
]
Julian Reschke commented on OAK-6782:
-
trunk: [r1811575|http://svn.apache.org/r1811575]
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> candidate_oak_1_6
> Fix For: 1.8, 1.7.9
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-6782.
-
Resolution: Fixed
Fix Version/s: 1.7.9
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> candidate_oak_1_6
> Fix For: 1.8, 1.7.9
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-4709) Test failure: ExternalPrivateStoreIT.testProxyFlippedIntermediateByte2
[
https://issues.apache.org/jira/browse/OAK-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196986#comment-16196986
]
Julian Reschke commented on OAK-4709:
-
These occasional test failures keep wasting our time. Can we disable those
tests?
> Test failure: ExternalPrivateStoreIT.testProxyFlippedIntermediateByte2
> --
>
> Key: OAK-4709
> URL: https://issues.apache.org/jira/browse/OAK-4709
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
>Affects Versions: 1.2.18, 1.4.6, 1.6.1
>Reporter: Julian Reschke
>
> This test reliably fails for me in 1.4 with:
> {noformat}
> testProxyFlippedIntermediateByte2(org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 1.3 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> {noformat}
> It does not fail in trunk, but that's because all ITs for tarmk-standby
> currently are skipped, because they are executed with fixture SEGMENT_TAR
> while the code checks for SEGMENT_MK.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6751) Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8
[ https://issues.apache.org/jira/browse/OAK-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196837#comment-16196837 ] Julian Reschke edited comment on OAK-6751 at 10/9/17 1:13 PM: -- 1.4: [r1811553|http://svn.apache.org/r1811553] 1.2: [r1811567|http://svn.apache.org/r1811567] was (Author: reschke): 1.4: [r1811553|http://svn.apache.org/r1811553] > Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8 > --- > > Key: OAK-6751 > URL: https://issues.apache.org/jira/browse/OAK-6751 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.2.28, 1.4.19 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6751) Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8
[ https://issues.apache.org/jira/browse/OAK-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6751: Fix Version/s: 1.2.28 > Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8 > --- > > Key: OAK-6751 > URL: https://issues.apache.org/jira/browse/OAK-6751 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.2.28, 1.4.19 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6782:
Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4
candidate_oak_1_6 (was: )
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> candidate_oak_1_6
> Fix For: 1.8
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6782:
Fix Version/s: 1.8
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> candidate_oak_1_6
> Fix For: 1.8
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6650) new release checksum requirements
[ https://issues.apache.org/jira/browse/OAK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196883#comment-16196883 ] Julian Reschke commented on OAK-6650: - Tried with the feature branch and the POM modification for testing, and it indeed generates an SHA1 file. (Is this what I was supposed to test?) > new release checksum requirements > - > > Key: OAK-6650 > URL: https://issues.apache.org/jira/browse/OAK-6650 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Davide Giannella >Assignee: Davide Giannella > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8 > > Attachments: OAK-6650-checkrelease.diff > > > As of various SHA algorithm the Apache policies around signatures and > checksums changed requiring to specify the sha algorithm as part of the file > extension: sha1, sha256, sha512. > http://www.apache.org/dev/release-distribution#sigs-and-sums > currently Oak signs with sha-1 and we should at least change the file > extension > h3. impacted areas > - release process (pom.xml) > - check release > - html download page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196865#comment-16196865
]
Tommaso Teofili commented on OAK-6790:
--
[~catholicon] sure, I guess this is not the only export we changed in that area.
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196852#comment-16196852
]
Julian Reschke commented on OAK-6782:
-
Looking at the MongoDS variant shows that we always invalidate after talking to
the persistence; and so so in the {{finally}} block. Will adjust RDB to do the
same.
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196838#comment-16196838
]
Vikas Saurabh edited comment on OAK-6790 at 10/9/17 11:54 AM:
--
[~teofili], yes, I realized that the package export is breaking backward
comatibility - I was assuming that we've done this for a lot other packages and
felt that it might be ok here too. I feel if we're ok to move it to a separate
bundle (to me query-spi feels better home), then we might be ok with package
update too.
was (Author: catholicon):
[~teofili], yes, I realized that the package export is breaking backward in
comatibility - I was assuming that we've done this for a lot other packages and
felt that it might be ok here too. I feel if we're ok to move it to a separate
bundle (to me query-spi feels better home), then we might be ok with package
update too.
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6797) DocumentStore conditional remove: EXISTS on non-revision property?
[
https://issues.apache.org/jira/browse/OAK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196847#comment-16196847
]
Julian Reschke commented on OAK-6797:
-
As far as I can tell, the only place (outside tests and wrappers) where the
conditional remove is used is in
{{org.apache.jackrabbit.oak.plugins.document.VersionGarbageCollector.DeletedDocsGC.removeDeletedDocuments(Iterator,
long, boolean, String)}}. In that case, only the variant with equals check for
MODIFIED is used.
> DocumentStore conditional remove: EXISTS on non-revision property?
> --
>
> Key: OAK-6797
> URL: https://issues.apache.org/jira/browse/OAK-6797
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
>Reporter: Julian Reschke
>Priority: Minor
> Attachments: OAK-6797.diff
>
>
> Implementations currently differ in whether the "Exists" condition works on a
> non-revision property.
> (RDBDS and MongoDS seem to support it, while MemoryDS does not).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196838#comment-16196838
]
Vikas Saurabh commented on OAK-6790:
[~teofili], yes, I realized that the package export is breaking backward in
comatibility - I was assuming that we've done this for a lot other packages and
felt that it might be ok here too. I feel if we're ok to move it to a separate
bundle (to me query-spi feels better home), then we might be ok with package
update too.
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6751) Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8
[ https://issues.apache.org/jira/browse/OAK-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196837#comment-16196837 ] Julian Reschke commented on OAK-6751: - 1.4: [r1811553|http://svn.apache.org/r1811553] > Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8 > --- > > Key: OAK-6751 > URL: https://issues.apache.org/jira/browse/OAK-6751 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.4.19 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6751) Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8
[ https://issues.apache.org/jira/browse/OAK-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-6751. - Resolution: Fixed Fix Version/s: 1.4.19 > Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8 > --- > > Key: OAK-6751 > URL: https://issues.apache.org/jira/browse/OAK-6751 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.4.19 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6803) Provide a way to for persistent cache to determine which all nodes are cached
Chetan Mehrotra created OAK-6803: Summary: Provide a way to for persistent cache to determine which all nodes are cached Key: OAK-6803 URL: https://issues.apache.org/jira/browse/OAK-6803 Project: Jackrabbit Oak Issue Type: Improvement Components: documentmk Reporter: Chetan Mehrotra Fix For: 1.8 Currently persistent cache if enabled for nodes caches all nodes accessed on the system. It would be better if it can be configured to only cache those nodes which are not volatile so that caching can be effective Purpose of this issue is to * Provide an extension point in PersistentCache logic to check if a node is to be cached * Provide an impl which relies on some static OSGi config to determine that Later we can make this impl dynamic i.e. rely on access pattern to cache imp stuff -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6802) Manage 'secret' property internally in S3/AzureDataStore
Amit Jain created OAK-6802: -- Summary: Manage 'secret' property internally in S3/AzureDataStore Key: OAK-6802 URL: https://issues.apache.org/jira/browse/OAK-6802 Project: Jackrabbit Oak Issue Type: Improvement Components: blob-cloud-azure, blob-cloud Reporter: Amit Jain Assignee: Amit Jain Fix For: 1.8 Property 'secret' is required to be configured (which is a shared secret among instances sharing the datastore) to enable binary-less replication. The DataStore should manage it internally as it does for other things in the META folder like in the container like repository ID etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6801) Set minRecordLength to the recommended 4096 in OakFileDataStore
Amit Jain created OAK-6801: -- Summary: Set minRecordLength to the recommended 4096 in OakFileDataStore Key: OAK-6801 URL: https://issues.apache.org/jira/browse/OAK-6801 Project: Jackrabbit Oak Issue Type: Improvement Components: blob-plugins Reporter: Amit Jain Assignee: Amit Jain Fix For: 1.8 The JR2 FileDataStore which OakFileDataStore extends has a default minRecordLength set to 100 while the recommendation is to use 4096 bytes. We should change the default to 4096 instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6790) FacetResult class isn't exposed anymore
[
https://issues.apache.org/jira/browse/OAK-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196770#comment-16196770
]
Tommaso Teofili commented on OAK-6790:
--
+1 to expose it, however I think this is a not backward compatible change as
{{FacetResult}} used to be exposed from _org.apache.jackrabbit.oak.query.facet_
package.
> FacetResult class isn't exposed anymore
> ---
>
> Key: OAK-6790
> URL: https://issues.apache.org/jira/browse/OAK-6790
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.2
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8
>
>
> OAK-3847 exposed {{FacetResult}} (rather
> {{org.apache.jackrabbit.oak.query.facet}} package) to easily consume
> extracted facet data. That exported package got removed during OAK-6304 (as
> noted in this comment \[1]).
> We need to export that class - maybe that class makes sense as part of
> {{oak-query-spi}} module - that still needs to be checked as assessed btw (ie
> if we can simply re-enable the removed export AND that its current place in
> oak-core still makes sense or not).
> [~anchela], would you remember what was the warning that was observed without
> removing this export (disclaimer: I still feel that it belongs in
> {{oak-query-spi}}... I'm just trying to have all data available).
> \[1]:
> https://issues.apache.org/jira/browse/OAK-6304?focusedCommentId=16042721=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042721
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6650) new release checksum requirements
[
https://issues.apache.org/jira/browse/OAK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6650:
--
Attachment: OAK-6650-checkrelease.diff
in [^OAK-6650-checkrelease.diff] a patch for the check-release script we use to
check the SHAs.
[~reschke] could you please check the feature branch and this patch? If ok, I
will
- commit feature branch to trunk
- backport to each oak branch
- update the {{check-release.sh}}
- resolve this issue.
This is the least possible change we can do to comply with apache requirements.
We can investigate discuss using SHA256 or greater in separate issues and
follow-up with bugs in case something won't work.
> new release checksum requirements
> -
>
> Key: OAK-6650
> URL: https://issues.apache.org/jira/browse/OAK-6650
> Project: Jackrabbit Oak
> Issue Type: Improvement
>Reporter: Davide Giannella
>Assignee: Davide Giannella
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> candidate_oak_1_6
> Fix For: 1.8
>
> Attachments: OAK-6650-checkrelease.diff
>
>
> As of various SHA algorithm the Apache policies around signatures and
> checksums changed requiring to specify the sha algorithm as part of the file
> extension: sha1, sha256, sha512.
> http://www.apache.org/dev/release-distribution#sigs-and-sums
> currently Oak signs with sha-1 and we should at least change the file
> extension
> h3. impacted areas
> - release process (pom.xml)
> - check release
> - html download page
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6650) new release checksum requirements
[
https://issues.apache.org/jira/browse/OAK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196683#comment-16196683
]
Davide Giannella commented on OAK-6650:
---
managed to manually check we have {{sha1}} extension by applying the following
patch on top of the feature branch and running {{mvn clean install
-Papache-release -DskipTests}}
{noformat}
diff --git a/pom.xml b/pom.xml
index 3b631c42b3..24d8bf2d95 100644
--- a/pom.xml
+++ b/pom.xml
@@ -182,7 +182,7 @@
run
-deploy
+package
{noformat}
> new release checksum requirements
> -
>
> Key: OAK-6650
> URL: https://issues.apache.org/jira/browse/OAK-6650
> Project: Jackrabbit Oak
> Issue Type: Improvement
>Reporter: Davide Giannella
>Assignee: Davide Giannella
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> candidate_oak_1_6
> Fix For: 1.8
>
>
> As of various SHA algorithm the Apache policies around signatures and
> checksums changed requiring to specify the sha algorithm as part of the file
> extension: sha1, sha256, sha512.
> http://www.apache.org/dev/release-distribution#sigs-and-sums
> currently Oak signs with sha-1 and we should at least change the file
> extension
> h3. impacted areas
> - release process (pom.xml)
> - check release
> - html download page
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196616#comment-16196616 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #848|https://builds.apache.org/job/Jackrabbit%20Oak/848/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/848/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6795) Build Jackrabbit Oak #844 failed
[ https://issues.apache.org/jira/browse/OAK-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196571#comment-16196571 ] Hudson commented on OAK-6795: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #847|https://builds.apache.org/job/Jackrabbit%20Oak/847/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/847/console] > Build Jackrabbit Oak #844 failed > > > Key: OAK-6795 > URL: https://issues.apache.org/jira/browse/OAK-6795 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #844 has failed. > First failed run: [Jackrabbit Oak > #844|https://builds.apache.org/job/Jackrabbit%20Oak/844/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/844/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6800) Minor typo in message returned by consistency check through mbean
[ https://issues.apache.org/jira/browse/OAK-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-6800. Resolution: Fixed http://svn.apache.org/viewvc?rev=1811536=rev > Minor typo in message returned by consistency check through mbean > - > > Key: OAK-6800 > URL: https://issues.apache.org/jira/browse/OAK-6800 > Project: Jackrabbit Oak > Issue Type: Bug > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain >Priority: Minor > Fix For: 1.8, 1.7.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6800) Minor typo in message returned by consistency check through mbean
Amit Jain created OAK-6800: -- Summary: Minor typo in message returned by consistency check through mbean Key: OAK-6800 URL: https://issues.apache.org/jira/browse/OAK-6800 Project: Jackrabbit Oak Issue Type: Bug Components: blob-plugins Reporter: Amit Jain Assignee: Amit Jain Priority: Minor Fix For: 1.8, 1.7.9 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6796) DataStoreTestBase.testSyncBigBlob failures
[
https://issues.apache.org/jira/browse/OAK-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Dulceanu reassigned OAK-6796:
Assignee: Andrei Dulceanu
> DataStoreTestBase.testSyncBigBlob failures
> --
>
> Key: OAK-6796
> URL: https://issues.apache.org/jira/browse/OAK-6796
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Attachments:
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt
>
>
> {noformat}
> ExternalPrivateStoreIT>DataStoreTestBase.testSyncBigBlob:237 expected:<{
> root = { ... } }> but was:<{ root : { } }>
> ExternalSharedStoreIT>DataStoreTestBase.testSyncBigBlob:237 expected:<{
> root = { ... } }> but was:<{ root : { } }>
> {noformat}
> fail reliably on my Windows notebook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6550) Make BlobTracker snaphot process smarter
[ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196548#comment-16196548 ] Amit Jain commented on OAK-6550: The problem on my setup (SegmentNodeStore) is * Active deletion deleted the blob on 4th * Compaction since then is skipped because there isn't enough garbage to clean up * Running consistency check reports failure since, the reference to the actively deleted garbage still exists. It will continue to fail until the compaction finally deletes it. > Make BlobTracker snaphot process smarter > > > Key: OAK-6550 > URL: https://issues.apache.org/jira/browse/OAK-6550 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8 > > > Currently, the BlobTracker snapshot() process is scheduled (every 12 hours by > default) which synchronizes the local additions & deletions since last change > with the datastore and consequently other cluster nodes. > The process should be slightly improved to run the sync on every removal i.e. > either through : > * Blob GC > * Active Deletion > And add some heuristic (most likely time based) to skip an upcoming sync > cycle if it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6550) Make BlobTracker snaphot process smarter
[ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196534#comment-16196534 ] Amit Jain commented on OAK-6550: [~catholicon] I have an instance where I also have a consistency check failure and here the BlobTracker is in sync with active deletions (I forced BlobTracker to not collect ids). I will check further to see what could be the reason. > Make BlobTracker snaphot process smarter > > > Key: OAK-6550 > URL: https://issues.apache.org/jira/browse/OAK-6550 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8 > > > Currently, the BlobTracker snapshot() process is scheduled (every 12 hours by > default) which synchronizes the local additions & deletions since last change > with the datastore and consequently other cluster nodes. > The process should be slightly improved to run the sync on every removal i.e. > either through : > * Blob GC > * Active Deletion > And add some heuristic (most likely time based) to skip an upcoming sync > cycle if it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5546) [BlobGC] Adapt time to delete blobs based on lucene indexing activity
[
https://issues.apache.org/jira/browse/OAK-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-5546:
---
Fix Version/s: 1.7.9
> [BlobGC] Adapt time to delete blobs based on lucene indexing activity
> -
>
> Key: OAK-5546
> URL: https://issues.apache.org/jira/browse/OAK-5546
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.9
>
>
> Blob GC deletes only those candidate blobs which are older from current than
> the configured {{blobGcMaxAgeInSecs}} interval (Default to 24 hours).
> This should be improved to take into time long running lucene re-indexing
> task which can potentially run into days for large repositories as otherwise
> it risks data loss and index corruption.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-5546) [BlobGC] Adapt time to delete blobs based on lucene indexing activity
[
https://issues.apache.org/jira/browse/OAK-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196532#comment-16196532
]
Amit Jain commented on OAK-5546:
Committed with http://svn.apache.org/viewvc?rev=1811532=rev
[~chetanm], [~catholicon] Could you please review
> [BlobGC] Adapt time to delete blobs based on lucene indexing activity
> -
>
> Key: OAK-5546
> URL: https://issues.apache.org/jira/browse/OAK-5546
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.8
>
>
> Blob GC deletes only those candidate blobs which are older from current than
> the configured {{blobGcMaxAgeInSecs}} interval (Default to 24 hours).
> This should be improved to take into time long running lucene re-indexing
> task which can potentially run into days for large repositories as otherwise
> it risks data loss and index corruption.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6799) OSGi service tests for Blob GC
[ https://issues.apache.org/jira/browse/OAK-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-6799. Resolution: Fixed Tests added with http://svn.apache.org/viewvc?rev=1811531=rev > OSGi service tests for Blob GC > -- > > Key: OAK-6799 > URL: https://issues.apache.org/jira/browse/OAK-6799 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8, 1.7.9 > > > OSGi initialization tests for Blob GC. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6798) Basic Blob GC test for in-memory NodeStore and BlobStore
[ https://issues.apache.org/jira/browse/OAK-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-6798. Resolution: Fixed Added with http://svn.apache.org/viewvc?rev=1811530=rev. > Basic Blob GC test for in-memory NodeStore and BlobStore > - > > Key: OAK-6798 > URL: https://issues.apache.org/jira/browse/OAK-6798 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8, 1.7.9 > > > Create a basic tests for BlobGC which can test the basic functionality using > an in-memory Node and Blob Store. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
