[jira] [Commented] (OAK-7503) Build Jackrabbit Oak #1448 failed
[ https://issues.apache.org/jira/browse/OAK-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483531#comment-16483531 ] Hudson commented on OAK-7503: - Build is still failing. Failed run: [Jackrabbit Oak #1452|https://builds.apache.org/job/Jackrabbit%20Oak/1452/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1452/console] > Build Jackrabbit Oak #1448 failed > - > > Key: OAK-7503 > URL: https://issues.apache.org/jira/browse/OAK-7503 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1448 has failed. > First failed run: [Jackrabbit Oak > #1448|https://builds.apache.org/job/Jackrabbit%20Oak/1448/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1448/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7503) Build Jackrabbit Oak #1448 failed
[ https://issues.apache.org/jira/browse/OAK-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482899#comment-16482899 ] Hudson commented on OAK-7503: - Build is still failing. Failed run: [Jackrabbit Oak #1451|https://builds.apache.org/job/Jackrabbit%20Oak/1451/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1451/console] > Build Jackrabbit Oak #1448 failed > - > > Key: OAK-7503 > URL: https://issues.apache.org/jira/browse/OAK-7503 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1448 has failed. > First failed run: [Jackrabbit Oak > #1448|https://builds.apache.org/job/Jackrabbit%20Oak/1448/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1448/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7410) Define SPIs for Oak Search module
[ https://issues.apache.org/jira/browse/OAK-7410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482745#comment-16482745 ] Tommaso Teofili commented on OAK-7410: -- committer first editor draft in r1831979. > Define SPIs for Oak Search module > - > > Key: OAK-7410 > URL: https://issues.apache.org/jira/browse/OAK-7410 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > Fix For: 1.10 > > > Abstract IndexEditor and QueryIndex implementations and SPIs should be > created for Oak Search module. > Those classes should be then reused / extended by implementors in and outside > Oak . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7410) Define SPIs for Oak Search module
[ https://issues.apache.org/jira/browse/OAK-7410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482709#comment-16482709 ] Tommaso Teofili commented on OAK-7410: -- this task can be split in more sub tasks: # create abstract index editor implementation # create abstract query index implementation # (optional) create test index implementation extending both editor and query index to make verify SPIs satisfy all requirements and constraints > Define SPIs for Oak Search module > - > > Key: OAK-7410 > URL: https://issues.apache.org/jira/browse/OAK-7410 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > Fix For: 1.10 > > > Abstract IndexEditor and QueryIndex implementations and SPIs should be > created for Oak Search module. > Those classes should be then reused / extended by implementors in and outside > Oak . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7503) Build Jackrabbit Oak #1448 failed
[ https://issues.apache.org/jira/browse/OAK-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482564#comment-16482564 ] Hudson commented on OAK-7503: - Build is still failing. Failed run: [Jackrabbit Oak #1450|https://builds.apache.org/job/Jackrabbit%20Oak/1450/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1450/console] > Build Jackrabbit Oak #1448 failed > - > > Key: OAK-7503 > URL: https://issues.apache.org/jira/browse/OAK-7503 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1448 has failed. > First failed run: [Jackrabbit Oak > #1448|https://builds.apache.org/job/Jackrabbit%20Oak/1448/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1448/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7499) Dependencies on various 'plugins'
[
https://issues.apache.org/jira/browse/OAK-7499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482535#comment-16482535
]
Robert Munteanu commented on OAK-7499:
--
[~anchela] - changes LGTM. For the components that don't have an {{activate}}
method that needs to do some work you can drop the {{immediate=true}} flag as
it's not needed.
> Dependencies on various 'plugins'
> -
>
> Key: OAK-7499
> URL: https://issues.apache.org/jira/browse/OAK-7499
> Project: Jackrabbit Oak
> Issue Type: Sub-task
>Reporter: angela
>Priority: Major
> Attachments: OAK-7499-adjustsecuritycode.patch,
> OAK-7499-extractplugins.patch
>
>
> subtask of OAK-7498 to drop usage of plugin classes directly from security
> code base:
> - extract interfaces for managers and provider services
> - replace usage of implementenations
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7501) Dependencies on IndexUtils
[
https://issues.apache.org/jira/browse/OAK-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482525#comment-16482525
]
Robert Munteanu commented on OAK-7501:
--
[~anchela] - changes overall look good to me.
Regarding the OSGi annotations - looking at the [\@Reference
javadoc|https://osgi.org/javadoc/r6/cmpn/org/osgi/service/component/annotations/Reference.html]
I think you can drop the _bind_ and _cardinality_ fields as the defaults are
suitable.
While looking at how the new {{QueryIndexCreator}} API is used, we seem to have
the following pattern:
- get index node from root node
- if index does not exist, create index with the following properties ...
It might be simpler to capture this in the API. One possibility would be to
have a single method {{ensureIndexDefinitionExists}} which takes the root node
and the index definition ( possibly as a new object ). Another one would be to
have a {{QueryIndexCreatorFactory}} ( or similar, I'm bad at naming ) which
creates a {{QueryIndexCreator}}, given a root node. The created
{{QueryIndexCreator}} can then expose more fine-grained operations, such as
{{ensureIndexDefinitionExists}} or the the current
{{hasIndexDefinition}}/{{createIndexDefintion}} .
I suggest these since it does not seem that intuitive/safe to pass
{{NodeBuilder}} objects around, like the old API did.
> Dependencies on IndexUtils
> --
>
> Key: OAK-7501
> URL: https://issues.apache.org/jira/browse/OAK-7501
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, indexing, security
>Reporter: angela
>Priority: Major
> Labels: m12n
> Attachments: OAK-7501-adjust_security.patch, OAK-7501-indexing.patch
>
>
> There are several places across the oak security code base where
> {{IndexUtils}} is used to create index definitions. In addition these usages
> hardcode implementation details on how the index definitions are stored.
> The goal is to make the security code independant of the very details of the
> index machinery and ultimately allow the indexing team to change/replace the
> way indices are store and how requirements like e.g. uniqueness are met.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7503) Build Jackrabbit Oak #1448 failed
[ https://issues.apache.org/jira/browse/OAK-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482486#comment-16482486 ] Hudson commented on OAK-7503: - Build is still failing. Failed run: [Jackrabbit Oak #1449|https://builds.apache.org/job/Jackrabbit%20Oak/1449/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1449/console] > Build Jackrabbit Oak #1448 failed > - > > Key: OAK-7503 > URL: https://issues.apache.org/jira/browse/OAK-7503 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1448 has failed. > First failed run: [Jackrabbit Oak > #1448|https://builds.apache.org/job/Jackrabbit%20Oak/1448/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1448/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6513) Journal based Async Indexer
[
https://issues.apache.org/jira/browse/OAK-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6513:
--
Fix Version/s: (was: 1.9.2)
> Journal based Async Indexer
> ---
>
> Key: OAK-6513
> URL: https://issues.apache.org/jira/browse/OAK-6513
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Major
> Fix For: 1.10, 1.9.3
>
>
> Current async indexer design is based on NodeState diff. This has served us
> fine so far however off late it is not able to perform well if rate of
> repository writes is high. When changes happen faster than index-update can
> process them, larger and larger diffs will happen. These make index-updates
> slower, which again lead to the next diff being ever larger than the one
> before (assuming a constant ingestion rate).
> In current diff based flow the indexer performs complete diff for all changes
> happening between 2 cycle. It may happen that lots of writes happens but not
> much indexable content is written. So doing diff there is a wasted effort.
> In 1.6 release for NRT Indexing we implemented a journal based indexing for
> external changes(OAK-4808, OAK-5430). That approach can be generalized and
> used for async indexing.
> Before talking about the journal based approach lets see how IndexEditor work
> currently
> h4. IndexEditor
> Currently any IndexEditor performs 2 tasks
> # Identify which node is to be indexed based on some index definition. The
> Editor gets invoked as part of content diff where it determines which
> NodeState is to be indexed
> # Update the index based on node to be indexed
> For e.g. in oak-lucene we have LuceneIndexEditor which identifies the
> NodeStates to be indexed and LuceneDocumentMaker which constructs the Lucene
> Document from NodeState to be indexed. For journal based approach we can
> decouple these 2 parts and thus have
> * IndexEditor - Identifies which all paths need to be indexed for given index
> definition
> * IndexUpdater - Updates the index based on given NodeState and its path
> h4. High Level Flow
> # Session Commit Flow
> ## Each index type would provide a IndexEditor which would be invoked as part
> of commit (like sync indexes). These IndexEditor would just determine which
> paths needs to be indexed.
> ## As part of commit the paths to be indexed would be written to journal.
> # AsyncIndexUpdate flow
> ## AsyncIndexUpdate would query this journal to fetch all such indexed paths
> between the 2 checkpoints
> ## Based on the index path data it would invoke the {{IndexUpdater}} to
> update the index for that path
> ## Merge the index updates
> h4. Benefits
> Such a design would have following impact
> # More work done as part of write
> # Marking of indexable content is distributed hence at indexing time lesser
> work to be done
> # Indexing can progress in batches
> # The indexers can be called in parallel
> h4. Journal Implementation
> DocumentNodeStore currently has an in built journal which is being used for
> NRT Indexing. That feature can be exposed as an api.
> For scaling index this design is mostly required for cluster case. So we can
> possibly have both indexing support implemented and use the journal based
> support for DocumentNodeStore setups. Or we can look into implementing such a
> journal for SegmentNodeStore setups also
> h4. Open Points
> * Journal support in SegmentNodeStore
> * Handling deletes.
> Detailed proposal -
> https://wiki.apache.org/jackrabbit/Journal%20based%20Async%20Indexer
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-5544) Improve indexing resilience
[ https://issues.apache.org/jira/browse/OAK-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5544: -- Fix Version/s: (was: 1.9.2) > Improve indexing resilience > --- > > Key: OAK-5544 > URL: https://issues.apache.org/jira/browse/OAK-5544 > Project: Jackrabbit Oak > Issue Type: Epic > Components: lucene >Reporter: Alexander Saar >Assignee: Chetan Mehrotra >Priority: Critical > Labels: resilience > Fix For: 1.10, 1.9.3 > > > grouping the improvements for indexer resilience in this issue for easier > tracking -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3437) Regression in org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5 when enabling OAK-1617
[
https://issues.apache.org/jira/browse/OAK-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3437:
--
Fix Version/s: (was: 1.9.2)
> Regression in org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5 when
> enabling OAK-1617
> --
>
> Key: OAK-3437
> URL: https://issues.apache.org/jira/browse/OAK-3437
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
>Reporter: Davide Giannella
>Assignee: Tommaso Teofili
>Priority: Major
> Fix For: 1.10, 1.9.3
>
>
> When enabling OAK-1617 (still to be committed) there's a regression in the
> {{oak-solr-core}} unit tests
> - {{org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR3}}
> - {{org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR4}}
> - {{org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5}}
> The WIP of the feature can be found in
> https://github.com/davidegiannella/jackrabbit-oak/tree/OAK-1617 and a full
> patch will be attached shortly for review in OAK-1617 itself.
> The feature is currently disabled, in order to enable it for unit testing an
> approach like this can be taken
> https://github.com/davidegiannella/jackrabbit-oak/blob/177df1a8073b1237857267e23d12a433e3d890a4/oak-core/src/test/java/org/apache/jackrabbit/oak/query/SQL2OptimiseQueryTest.java#L142
> or setting the system property {{-Doak.query.sql2optimisation}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6166) Support versioning in the federated node store
[ https://issues.apache.org/jira/browse/OAK-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6166: -- Fix Version/s: (was: 1.9.2) > Support versioning in the federated node store > -- > > Key: OAK-6166 > URL: https://issues.apache.org/jira/browse/OAK-6166 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: composite >Reporter: Tomek Rękawek >Priority: Minor > Fix For: 1.10, 1.9.3 > > > The mount info provider should affect the versioning code as well, so version > histories for the mounted paths are stored separately. Similarly to what we > have in the indexing, let's store the mounted version histories under: > /jcr:system/jcr:versionStorage/:oak:mount-MOUNTNAME -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5776) Build failure: Cannot create directory : Filename too long
[ https://issues.apache.org/jira/browse/OAK-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5776: -- Fix Version/s: (was: 1.9.2) > Build failure: Cannot create directory : Filename too long > -- > > Key: OAK-5776 > URL: https://issues.apache.org/jira/browse/OAK-5776 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > Labels: CI, build-failure, test-failure, windows > Fix For: 1.10, 1.9.3 > > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) > 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #473 > has failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited > security) 64-bit Windows > only,nsfixtures=DOCUMENT_NS,profile=integrationTesting > #473|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=integrationTesting/473/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=integrationTesting/473/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6098) Build timeout
[
https://issues.apache.org/jira/browse/OAK-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6098:
--
Fix Version/s: (was: 1.9.2)
> Build timeout
> -
>
> Key: OAK-6098
> URL: https://issues.apache.org/jira/browse/OAK-6098
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
> Labels: CI, jenkins, test-failure
> Fix For: 1.10, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #175 has failed.
> First failed run: [Jackrabbit Oak
> #175|https://builds.apache.org/job/Jackrabbit%20Oak/175/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/175/console]
> This build timed out on node https://builds.apache.org/computer/H10. Usually
> the build takes around 40mins.
> {code}
> Build timed out (after 60 minutes). Marking the build as failed.
> {code}
> Also timed out on https://builds.apache.org/computer/cassandra5. See
> https://builds.apache.org/view/J/job/Jackrabbit%20Oak/208/
> Also timed out on https://builds.apache.org/computer/ubuntu-eu2. See
> https://builds.apache.org/job/Jackrabbit%20Oak/246/
> Also timed out on https://builds.apache.org/computer/ubuntu-2. See
> https://builds.apache.org/job/Jackrabbit%20Oak/267/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-5923) Document S3 datastore
[ https://issues.apache.org/jira/browse/OAK-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5923: -- Fix Version/s: (was: 1.9.2) > Document S3 datastore > - > > Key: OAK-5923 > URL: https://issues.apache.org/jira/browse/OAK-5923 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: blob, doc >Reporter: Alexander Klimetschek >Assignee: Amit Jain >Priority: Major > Fix For: 1.10, 1.9.3 > > > The S3 datastore is currently hardly documented. > The [generic blobstore > documentation|http://jackrabbit.apache.org/oak/docs/plugins/blobstore.html] > is very much focused about the internal class structures, but quite confusing > for someone who wants to configure a specific datastore such as file and s3 > (the only ones right now). S3 settings are not documented at all, the [config > page|http://jackrabbit.apache.org/oak/docs/osgi_config.html#config-blobstore] > only mentions the generic maxCachedBinarySize and cacheSizeInMB. > The best bet is the [Adobe AEM product > documentation|https://docs.adobe.com/docs/en/aem/6-2/deploy/platform/data-store-config.html], > but that is for an older version and a few things changed since then. > Specific items below. Some have been confusing people using oak-blob-cloud > 1.5.15: > - "secret" property unclear (new) > - secretKey & accessKey can be omitted to leverage IAM roles (new) > - drop of proactiveCaching property (new) > - aws bucket/region/etc. settings > - config options (timeout, retries, threads) > - understanding caching behavior and performance optimization > - shared vs. non-shared options > - migrating from a previous version, how to update the config > - requirements on the AWS (account) side -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3355) Test failure: SpellcheckTest.testSpellcheckMultipleWords
[
https://issues.apache.org/jira/browse/OAK-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3355:
--
Fix Version/s: (was: 1.9.2)
> Test failure: SpellcheckTest.testSpellcheckMultipleWords
>
>
> Key: OAK-3355
> URL: https://issues.apache.org/jira/browse/OAK-3355
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
>Affects Versions: 1.0.24
> Environment:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
>Reporter: Michael Dürig
>Assignee: Tommaso Teofili
>Priority: Major
> Labels: ci, jenkins, test, test-failure
> Fix For: 1.10, 1.9.3
>
>
> {{org.apache.jackrabbit.oak.jcr.query.SpellcheckTest.testSpellcheckMultipleWords}}
> fails on Jenkins.
> Failure seen at builds: 389, 392, 395, 396, 562
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/396/jdk=jdk-1.6u45,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/console
> {noformat}
> testSpellcheckMultipleWords(org.apache.jackrabbit.oak.jcr.query.SpellcheckTest)
> Time elapsed: 0.907 sec <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[voting[ in] ontario]> but
> was:<[voting[, voted,] ontario]>
> at junit.framework.Assert.assertEquals(Assert.java:85)
> at junit.framework.Assert.assertEquals(Assert.java:91)
> at
> org.apache.jackrabbit.oak.jcr.query.SpellcheckTest.testSpellcheckMultipleWords(SpellcheckTest.java:86)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6433) Remove baseline plugin configuration referring to oak-core after 1.8 release
[ https://issues.apache.org/jira/browse/OAK-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6433: -- Fix Version/s: (was: 1.9.2) > Remove baseline plugin configuration referring to oak-core after 1.8 release > > > Key: OAK-6433 > URL: https://issues.apache.org/jira/browse/OAK-6433 > Project: Jackrabbit Oak > Issue Type: Task > Components: api, blob-plugins, composite, core-spi, store-spi >Reporter: Chetan Mehrotra >Priority: Major > Fix For: 1.10, 1.9.3 > > > After 1.8 release and before 1.9.0 release we would need to readjust the > baseline plugin config. Currently for following modules the base artifactId > is set to oak-core as these modules were derived from oak-core as part of > m18n effort (OAK-6346) > * oak-api > * oak-blob-plugins > * oak-core-spi > * oak-store-spi > * oak-store-composite > So before 1.9.0 release these config should be removed so that these modules > can refer to last stable release from 1.8 branch where the current module > would have an existing release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-4524) LucenePropertyIndexTest#longRepExcerpt sometimes failing
[ https://issues.apache.org/jira/browse/OAK-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-4524: -- Fix Version/s: (was: 1.9.2) > LucenePropertyIndexTest#longRepExcerpt sometimes failing > > > Key: OAK-4524 > URL: https://issues.apache.org/jira/browse/OAK-4524 > Project: Jackrabbit Oak > Issue Type: Test > Components: lucene >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > Fix For: 1.10, 1.9.3 > > > As reported by Julian on oak-dev@ it seems _longRepExcerpt_ is still failing > sometimes when query takes more than 10s e.g. see this [Jenkins > failure|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1000/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.plugins.index.lucene/LucenePropertyIndexTest/longRepExcerpt/]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7263) oak-lucene should not depend on oak-store-document
[
https://issues.apache.org/jira/browse/OAK-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-7263:
--
Fix Version/s: (was: 1.9.2)
> oak-lucene should not depend on oak-store-document
> --
>
> Key: OAK-7263
> URL: https://issues.apache.org/jira/browse/OAK-7263
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: 1.10, 1.9.3
>
>
> {{oak-lucene}} has a hard dependency on {{oak-store-document}} and that looks
> wrong to me.
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project oak-lucene: Compilation failure: Compilation
> failure:
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneDocumentHolder.java:[31,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneDocumentHolder.java:[37,46]
> cannot find symbol
> [ERROR] symbol: class JournalProperty
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[33,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[34,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[38,47]
> cannot find symbol
> [ERROR] symbol: class JournalPropertyBuilder
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[106,12]
> cannot find symbol
> [ERROR] symbol: class JournalProperty
> [ERROR] location: class
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.LuceneJournalPropertyBuilder
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/LuceneIndexProviderService.java:[55,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/IndexedPaths.java:[29,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/IndexedPaths.java:[33,31]
> cannot find symbol
> [ERROR] symbol: class JournalProperty
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[22,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[23,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[25,54]
> cannot find symbol
> [ERROR] symbol: class JournalPropertyService
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[33,12]
> cannot find symbol
> [ERROR] symbol: class JournalPropertyBuilder
> [ERROR] location: class
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.LuceneJournalPropertyService
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[50,5]
> method does not override or implement a method from a supertype
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[61,5]
> method does not override or implement a method from a supertype
> [ERROR]
>
[jira] [Updated] (OAK-7358) Remove all usage of java.security.acl.Group for Java 12
[ https://issues.apache.org/jira/browse/OAK-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-7358: -- Fix Version/s: (was: 1.9.2) > Remove all usage of java.security.acl.Group for Java 12 > --- > > Key: OAK-7358 > URL: https://issues.apache.org/jira/browse/OAK-7358 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: security >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Major > Fix For: 1.10, 1.9.3 > > > Followup of OAK-7024 for the actual removal of the Group class from the > codebase to be java 11 compliant. > Not sure what to use for 'fix version', I went with 1.9.0 so this remains on > the radar, but we can push it out as needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6957) Remove export for org.apache.jackrabbit.oak.security
[
https://issues.apache.org/jira/browse/OAK-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6957:
--
Fix Version/s: (was: 1.9.2)
> Remove export for org.apache.jackrabbit.oak.security
>
>
> Key: OAK-6957
> URL: https://issues.apache.org/jira/browse/OAK-6957
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, security
>Reporter: angela
>Priority: Major
> Fix For: 1.10, 1.9.3
>
>
> [~stillalex], with the fix you provided for the {{Jcr}} class we should be
> able drop the export for _org.apache.jackrabbit.oak.security_
> Looking for remaining usages I noticed OAK-6956, which I will link to this
> issue.
> Apart from that, what's your take on this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-2155) TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
[
https://issues.apache.org/jira/browse/OAK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-2155:
--
Fix Version/s: (was: 1.9.2)
> TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
>
>
> Key: OAK-2155
> URL: https://issues.apache.org/jira/browse/OAK-2155
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, pojosr
>Reporter: Amit Jain
>Assignee: Alex Deparvu
>Priority: Major
> Labels: CI, test, ubuntu
> Fix For: 1.10, 1.9.3
>
>
> The test
> {{org.apache.jackrabbit.oak.run.osgi.TokenAuthenticationTest#tokenCreationWithPreAuth}}
> in oak-pojosr component failing repeatedly on the local system.
> Also, failing repeatedly on http://ci.apache.org/builders/oak-trunk-win7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6069) Modularisation of Oak
[ https://issues.apache.org/jira/browse/OAK-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6069: -- Fix Version/s: (was: 1.9.2) > Modularisation of Oak > - > > Key: OAK-6069 > URL: https://issues.apache.org/jira/browse/OAK-6069 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: angela >Priority: Major > Labels: modularization > Fix For: 1.10, 1.9.3 > > > Epic to track individual steps towards improved modularisation of Oak > Until now Oak modules are all released together, which has some drawbacks. > Work on the modules must be somewhat kept in lockstep. Releasing a fix for a > module means all other modules must be in a state that can be released as > well. For a user it may be desirable to just update a single module to get a > fix and not a complete set of Oak bundles. > The general approach for this epic should be to modularize only as needed and > not split everything. Obvious candidates are stable interfaces like Oak and > NodeStore API and NodeStore implementations. > This requires fixing potential circular dependencies between logical modules > we want to split up. We need a better distinction between the interface part > of the SPI and its implementations. Utilities and commons code must be > reviewed and potentially moved. > The oak-it related dependencies should be reconsidered and that a development > version of a NodeStore implementation can run integration tests. With the > current dependency setup a release of the NodeStore implementation is > required first to run the integration tests with those changes. > Some modules will probably be moved to the top-level and have their own > branches and tags. > To avoid branches it is important to always have trunk stable. Feature work > must happen on feature branches, in a forked module or protected with a > feature flag until it is ready for prime time. No more unstable work in trunk. > Module owner is primarily responsible for module releases. At some point > there won't be a dedicated person anymore responsible for 'the Oak release'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7224) oak-run check should have an option to check the segments checksums
[
https://issues.apache.org/jira/browse/OAK-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-7224:
--
Fix Version/s: (was: 1.9.2)
> oak-run check should have an option to check the segments checksums
> ---
>
> Key: OAK-7224
> URL: https://issues.apache.org/jira/browse/OAK-7224
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: tooling
> Fix For: 1.10, 1.9.3
>
>
> {{oak-run check}} does currently *not* check the checksums of the segments.
> As a consequence, there is no quick way of determining the state of the
> repository (corrupt/valid), after corrupting some random node record, as we
> currently do in {{CheckRepositoryTestBase#corruptRecord}}. To determine that,
> there needs to be an attempt to read the corrupt record as part of a
> traversal.
> An easier way would be to have a new dedicated option for this (i.e.,
> {{--segments}}) which checks by default the content of segments against the
> checksums from all the tar files in the specified location. Additionally, it
> could accept as an argument a list of tar files, the segments of which to be
> checked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6062) Test failure: CopyBinariesTest.validateMigration
[
https://issues.apache.org/jira/browse/OAK-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6062:
--
Fix Version/s: (was: 1.9.2)
> Test failure: CopyBinariesTest.validateMigration
>
>
> Key: OAK-6062
> URL: https://issues.apache.org/jira/browse/OAK-6062
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, documentmk
>Reporter: Hudson
>Priority: Major
> Labels: CI, flaky-test, jenkins, test-failure
> Fix For: 1.10, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #146 has failed.
> First failed run: [Jackrabbit Oak
> #146|https://builds.apache.org/job/Jackrabbit%20Oak/146/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/146/console]
> The test failure is:
> {noformat}
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest
> validateMigration[Copy references, no blobstores defined, document ->
> segment-tar](org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest)
> Time elapsed: 2.534 sec <<< ERROR!
> javax.jcr.RepositoryException: Failed to copy content
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> Caused by: java.lang.IllegalStateException: Branch with failed reset
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakOak0100:
> Branch reset failed
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> Caused by: org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> Empty branch cannot be reset
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7074) Ensure that all Documents are read with document order traversal indexing
[ https://issues.apache.org/jira/browse/OAK-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-7074: -- Fix Version/s: (was: 1.9.2) > Ensure that all Documents are read with document order traversal indexing > - > > Key: OAK-7074 > URL: https://issues.apache.org/jira/browse/OAK-7074 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: mongomk, run >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.10, 1.9.3 > > > With OAK-6353 support was added for document order traversal indexing. In > this mode we open a DB cursor and try to read all documents from it using > document order traversal. Such a cursor may remain open for long time (2-4 > hrs) and its possible that document may get reordered by the Mongo storage > engine. This would result in 2 aspects to be thought about > # Duplicate documents - Same document may appear more than once in result set > # Possibly missed document - It may be a possibility that a document got > moved and missed becoming part of cursor. > Both these aspects would need to be handled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7459) oak-run compact should support Azure Segment Store
[
https://issues.apache.org/jira/browse/OAK-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-7459:
--
Fix Version/s: (was: 1.9.2)
> oak-run compact should support Azure Segment Store
> --
>
> Key: OAK-7459
> URL: https://issues.apache.org/jira/browse/OAK-7459
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
> Labels: tooling
> Fix For: 1.10, 1.9.3
>
>
> {{oak-run compact}} should accept Azure URIs for the segment store in order
> to enable OffRC for Azure Segment Store. Proposed options to add:
> * {{azure-connection}}: connection URL to to connect to the Azure Storage
> * {{azure-container}}: name of the container to use
> * {{azure-root-path}}: segment store directory
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6914) Improve indexing progress estimates with multiple includes
[ https://issues.apache.org/jira/browse/OAK-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6914: -- Fix Version/s: (was: 1.9.2) > Improve indexing progress estimates with multiple includes > -- > > Key: OAK-6914 > URL: https://issues.apache.org/jira/browse/OAK-6914 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.10, 1.9.3 > > > With OAK-5970 support was added for providing ETA as indexing progresses. > However as discussed in the issue this estimate might not be good if indexes > have multiple include and excludes > Purpose of this task is to look for ways to improve it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6264) Test failure: IllegalArgumentException during upgrade tests
[
https://issues.apache.org/jira/browse/OAK-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6264:
--
Fix Version/s: (was: 1.9.2)
> Test failure: IllegalArgumentException during upgrade tests
>
>
> Key: OAK-6264
> URL: https://issues.apache.org/jira/browse/OAK-6264
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, upgrade
>Reporter: Hudson
>Priority: Major
> Labels: CI, jenkins, test-failure
> Fix For: 1.10, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #338 has failed.
> First failed run: [Jackrabbit Oak
> #338|https://builds.apache.org/job/Jackrabbit%20Oak/338/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/338/console]
> {noformat}
> javax.jcr.RepositoryException: Failed to copy content
> Stacktrace
> java.lang.RuntimeException: javax.jcr.RepositoryException: Failed to copy
> content
> at
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.prepare(CopyCheckpointsTest.java:141)
> Caused by: javax.jcr.RepositoryException: Failed to copy content
> at
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.prepare(CopyCheckpointsTest.java:141)
> Caused by: java.lang.IllegalArgumentException
> at
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.prepare(CopyCheckpointsTest.java:141)
> {noformat}
> This affects
> {noformat}
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Suppress
> the warning]
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Source
> data store defined, checkpoints migrated]
>
> org.apache.jackrabbit.oak.upgrade.IgnoreMissingBinariesTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.UpgradeOldSegmentTest.upgradeFrom10
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToJdbcTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment-tar -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to embedded, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to external, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to embedded, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to external, src blobstore defined]
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFbsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFdsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FdsToFbsTest.validateMigration
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-3809) Test failure: FacetTest
[
https://issues.apache.org/jira/browse/OAK-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3809:
--
Fix Version/s: (was: 1.9.2)
> Test failure: FacetTest
> ---
>
> Key: OAK-3809
> URL: https://issues.apache.org/jira/browse/OAK-3809
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
> Environment:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
>Reporter: Michael Dürig
>Assignee: Tommaso Teofili
>Priority: Major
> Labels: ci, jenkins, test, test-failure
> Fix For: 1.10, 1.9.3
>
>
> {{org.apache.jackrabbit.oak.jcr.query.FacetTest}} keeps failing on Jenkins:
> {noformat}
> testFacetRetrievalMV(org.apache.jackrabbit.oak.jcr.query.FacetTest) Time
> elapsed: 5.927 sec <<< FAILURE!
> junit.framework.ComparisonFailure: expected: (2), aem (1), apache (1), cosmetics (1), furniture (1)], tags:[repository
> (2), software (2), aem (1), apache (1), cosmetics (1), furniture (1)],
> tags:[repository (2), software (2), aem (1), apache (1), cosmetics (1),
> furniture (1)], tags:[repository (2), software (2), aem (1), apache (1),
> cosmetics (1), furniture (1)]]> but was:
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.jackrabbit.oak.jcr.query.FacetTest.testFacetRetrievalMV(FacetTest.java:80)
> {noformat}
> Failure seen at builds: 628, 629, 630, 633, 634, 636, 642, 643, 644, 645,
> 648, 651, 656, 659, 660, 663, 666
> See e.g.
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/634/#showFailuresLink
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6288) Test failure: upgrade tests failing: Failed to copy content
[
https://issues.apache.org/jira/browse/OAK-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6288:
--
Fix Version/s: (was: 1.9.2)
> Test failure: upgrade tests failing: Failed to copy content
> ---
>
> Key: OAK-6288
> URL: https://issues.apache.org/jira/browse/OAK-6288
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, upgrade
>Reporter: Hudson
>Priority: Major
> Labels: CI, jenkins, test-failure
> Fix For: 1.10, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #364 has failed.
> First failed run: [Jackrabbit Oak
> #364|https://builds.apache.org/job/Jackrabbit%20Oak/364/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/364/console]
> Failing tests:
> {noformat}
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Suppress
> the warning]
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Source
> data store defined, checkpoints migrated]
>
> org.apache.jackrabbit.oak.upgrade.IgnoreMissingBinariesTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.UpgradeOldSegmentTest.upgradeFrom10
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToJdbcTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment-tar -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to embedded, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to external, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to embedded, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to external, src blobstore defined]
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFbsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFdsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FdsToFbsTest.validateMigration
> {noformat}
> All seem to fail with
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.737
> s <<< FAILURE! - in
> org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest
> [ERROR]
> validateMigration(org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest)
> Time elapsed: 3.73 s <<< ERROR!
> java.lang.RuntimeException: javax.jcr.RepositoryException: Failed to copy
> content
> Caused by: javax.jcr.RepositoryException: Failed to copy content
> Caused by: java.lang.IllegalArgumentException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-5792) TarMK: Implement tooling to repair broken nodes
[
https://issues.apache.org/jira/browse/OAK-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5792:
--
Fix Version/s: (was: 1.9.2)
> TarMK: Implement tooling to repair broken nodes
> ---
>
> Key: OAK-5792
> URL: https://issues.apache.org/jira/browse/OAK-5792
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: run, segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
>Priority: Major
> Labels: production, tooling
> Fix For: 1.10, 1.9.3
>
>
> With {{oak-run check}} we can determine the last good revision of a
> repository and use it to manually roll back a corrupted segment store.
> Complementary to this we should implement a tool to roll forward a broken
> revision to a fixed new revision. Such a tool needs to detect which items are
> affected by a corruption and replace these items with markers. With this the
> repository could brought back online and the markers could be used to
> identify the locations in the tree where further manual action might be
> needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7358) Remove all usage of java.security.acl.Group for Java 12
[ https://issues.apache.org/jira/browse/OAK-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-7358: -- Fix Version/s: 1.9.3 > Remove all usage of java.security.acl.Group for Java 12 > --- > > Key: OAK-7358 > URL: https://issues.apache.org/jira/browse/OAK-7358 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: security >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Major > Fix For: 1.10, 1.9.2, 1.9.3 > > > Followup of OAK-7024 for the actual removal of the Group class from the > codebase to be java 11 compliant. > Not sure what to use for 'fix version', I went with 1.9.0 so this remains on > the radar, but we can push it out as needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6098) Build timeout
[
https://issues.apache.org/jira/browse/OAK-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6098:
--
Fix Version/s: 1.9.3
> Build timeout
> -
>
> Key: OAK-6098
> URL: https://issues.apache.org/jira/browse/OAK-6098
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
> Labels: CI, jenkins, test-failure
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #175 has failed.
> First failed run: [Jackrabbit Oak
> #175|https://builds.apache.org/job/Jackrabbit%20Oak/175/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/175/console]
> This build timed out on node https://builds.apache.org/computer/H10. Usually
> the build takes around 40mins.
> {code}
> Build timed out (after 60 minutes). Marking the build as failed.
> {code}
> Also timed out on https://builds.apache.org/computer/cassandra5. See
> https://builds.apache.org/view/J/job/Jackrabbit%20Oak/208/
> Also timed out on https://builds.apache.org/computer/ubuntu-eu2. See
> https://builds.apache.org/job/Jackrabbit%20Oak/246/
> Also timed out on https://builds.apache.org/computer/ubuntu-2. See
> https://builds.apache.org/job/Jackrabbit%20Oak/267/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7224) oak-run check should have an option to check the segments checksums
[
https://issues.apache.org/jira/browse/OAK-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-7224:
--
Fix Version/s: 1.9.3
> oak-run check should have an option to check the segments checksums
> ---
>
> Key: OAK-7224
> URL: https://issues.apache.org/jira/browse/OAK-7224
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: tooling
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> {{oak-run check}} does currently *not* check the checksums of the segments.
> As a consequence, there is no quick way of determining the state of the
> repository (corrupt/valid), after corrupting some random node record, as we
> currently do in {{CheckRepositoryTestBase#corruptRecord}}. To determine that,
> there needs to be an attempt to read the corrupt record as part of a
> traversal.
> An easier way would be to have a new dedicated option for this (i.e.,
> {{--segments}}) which checks by default the content of segments against the
> checksums from all the tar files in the specified location. Additionally, it
> could accept as an argument a list of tar files, the segments of which to be
> checked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6957) Remove export for org.apache.jackrabbit.oak.security
[
https://issues.apache.org/jira/browse/OAK-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6957:
--
Fix Version/s: 1.9.3
> Remove export for org.apache.jackrabbit.oak.security
>
>
> Key: OAK-6957
> URL: https://issues.apache.org/jira/browse/OAK-6957
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, security
>Reporter: angela
>Priority: Major
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> [~stillalex], with the fix you provided for the {{Jcr}} class we should be
> able drop the export for _org.apache.jackrabbit.oak.security_
> Looking for remaining usages I noticed OAK-6956, which I will link to this
> issue.
> Apart from that, what's your take on this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-5923) Document S3 datastore
[ https://issues.apache.org/jira/browse/OAK-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5923: -- Fix Version/s: 1.9.3 > Document S3 datastore > - > > Key: OAK-5923 > URL: https://issues.apache.org/jira/browse/OAK-5923 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: blob, doc >Reporter: Alexander Klimetschek >Assignee: Amit Jain >Priority: Major > Fix For: 1.10, 1.9.2, 1.9.3 > > > The S3 datastore is currently hardly documented. > The [generic blobstore > documentation|http://jackrabbit.apache.org/oak/docs/plugins/blobstore.html] > is very much focused about the internal class structures, but quite confusing > for someone who wants to configure a specific datastore such as file and s3 > (the only ones right now). S3 settings are not documented at all, the [config > page|http://jackrabbit.apache.org/oak/docs/osgi_config.html#config-blobstore] > only mentions the generic maxCachedBinarySize and cacheSizeInMB. > The best bet is the [Adobe AEM product > documentation|https://docs.adobe.com/docs/en/aem/6-2/deploy/platform/data-store-config.html], > but that is for an older version and a few things changed since then. > Specific items below. Some have been confusing people using oak-blob-cloud > 1.5.15: > - "secret" property unclear (new) > - secretKey & accessKey can be omitted to leverage IAM roles (new) > - drop of proactiveCaching property (new) > - aws bucket/region/etc. settings > - config options (timeout, retries, threads) > - understanding caching behavior and performance optimization > - shared vs. non-shared options > - migrating from a previous version, how to update the config > - requirements on the AWS (account) side -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-5792) TarMK: Implement tooling to repair broken nodes
[
https://issues.apache.org/jira/browse/OAK-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5792:
--
Fix Version/s: 1.9.3
> TarMK: Implement tooling to repair broken nodes
> ---
>
> Key: OAK-5792
> URL: https://issues.apache.org/jira/browse/OAK-5792
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: run, segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
>Priority: Major
> Labels: production, tooling
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> With {{oak-run check}} we can determine the last good revision of a
> repository and use it to manually roll back a corrupted segment store.
> Complementary to this we should implement a tool to roll forward a broken
> revision to a fixed new revision. Such a tool needs to detect which items are
> affected by a corruption and replace these items with markers. With this the
> repository could brought back online and the markers could be used to
> identify the locations in the tree where further manual action might be
> needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6069) Modularisation of Oak
[ https://issues.apache.org/jira/browse/OAK-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6069: -- Fix Version/s: 1.9.3 > Modularisation of Oak > - > > Key: OAK-6069 > URL: https://issues.apache.org/jira/browse/OAK-6069 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: angela >Priority: Major > Labels: modularization > Fix For: 1.10, 1.9.2, 1.9.3 > > > Epic to track individual steps towards improved modularisation of Oak > Until now Oak modules are all released together, which has some drawbacks. > Work on the modules must be somewhat kept in lockstep. Releasing a fix for a > module means all other modules must be in a state that can be released as > well. For a user it may be desirable to just update a single module to get a > fix and not a complete set of Oak bundles. > The general approach for this epic should be to modularize only as needed and > not split everything. Obvious candidates are stable interfaces like Oak and > NodeStore API and NodeStore implementations. > This requires fixing potential circular dependencies between logical modules > we want to split up. We need a better distinction between the interface part > of the SPI and its implementations. Utilities and commons code must be > reviewed and potentially moved. > The oak-it related dependencies should be reconsidered and that a development > version of a NodeStore implementation can run integration tests. With the > current dependency setup a release of the NodeStore implementation is > required first to run the integration tests with those changes. > Some modules will probably be moved to the top-level and have their own > branches and tags. > To avoid branches it is important to always have trunk stable. Feature work > must happen on feature branches, in a forked module or protected with a > feature flag until it is ready for prime time. No more unstable work in trunk. > Module owner is primarily responsible for module releases. At some point > there won't be a dedicated person anymore responsible for 'the Oak release'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3355) Test failure: SpellcheckTest.testSpellcheckMultipleWords
[
https://issues.apache.org/jira/browse/OAK-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3355:
--
Fix Version/s: 1.9.3
> Test failure: SpellcheckTest.testSpellcheckMultipleWords
>
>
> Key: OAK-3355
> URL: https://issues.apache.org/jira/browse/OAK-3355
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
>Affects Versions: 1.0.24
> Environment:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
>Reporter: Michael Dürig
>Assignee: Tommaso Teofili
>Priority: Major
> Labels: ci, jenkins, test, test-failure
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> {{org.apache.jackrabbit.oak.jcr.query.SpellcheckTest.testSpellcheckMultipleWords}}
> fails on Jenkins.
> Failure seen at builds: 389, 392, 395, 396, 562
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/396/jdk=jdk-1.6u45,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/console
> {noformat}
> testSpellcheckMultipleWords(org.apache.jackrabbit.oak.jcr.query.SpellcheckTest)
> Time elapsed: 0.907 sec <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[voting[ in] ontario]> but
> was:<[voting[, voted,] ontario]>
> at junit.framework.Assert.assertEquals(Assert.java:85)
> at junit.framework.Assert.assertEquals(Assert.java:91)
> at
> org.apache.jackrabbit.oak.jcr.query.SpellcheckTest.testSpellcheckMultipleWords(SpellcheckTest.java:86)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-2155) TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
[
https://issues.apache.org/jira/browse/OAK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-2155:
--
Fix Version/s: 1.9.3
> TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
>
>
> Key: OAK-2155
> URL: https://issues.apache.org/jira/browse/OAK-2155
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, pojosr
>Reporter: Amit Jain
>Assignee: Alex Deparvu
>Priority: Major
> Labels: CI, test, ubuntu
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> The test
> {{org.apache.jackrabbit.oak.run.osgi.TokenAuthenticationTest#tokenCreationWithPreAuth}}
> in oak-pojosr component failing repeatedly on the local system.
> Also, failing repeatedly on http://ci.apache.org/builders/oak-trunk-win7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6433) Remove baseline plugin configuration referring to oak-core after 1.8 release
[ https://issues.apache.org/jira/browse/OAK-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6433: -- Fix Version/s: 1.9.3 > Remove baseline plugin configuration referring to oak-core after 1.8 release > > > Key: OAK-6433 > URL: https://issues.apache.org/jira/browse/OAK-6433 > Project: Jackrabbit Oak > Issue Type: Task > Components: api, blob-plugins, composite, core-spi, store-spi >Reporter: Chetan Mehrotra >Priority: Major > Fix For: 1.10, 1.9.2, 1.9.3 > > > After 1.8 release and before 1.9.0 release we would need to readjust the > baseline plugin config. Currently for following modules the base artifactId > is set to oak-core as these modules were derived from oak-core as part of > m18n effort (OAK-6346) > * oak-api > * oak-blob-plugins > * oak-core-spi > * oak-store-spi > * oak-store-composite > So before 1.9.0 release these config should be removed so that these modules > can refer to last stable release from 1.8 branch where the current module > would have an existing release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6264) Test failure: IllegalArgumentException during upgrade tests
[
https://issues.apache.org/jira/browse/OAK-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6264:
--
Fix Version/s: 1.9.3
> Test failure: IllegalArgumentException during upgrade tests
>
>
> Key: OAK-6264
> URL: https://issues.apache.org/jira/browse/OAK-6264
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, upgrade
>Reporter: Hudson
>Priority: Major
> Labels: CI, jenkins, test-failure
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #338 has failed.
> First failed run: [Jackrabbit Oak
> #338|https://builds.apache.org/job/Jackrabbit%20Oak/338/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/338/console]
> {noformat}
> javax.jcr.RepositoryException: Failed to copy content
> Stacktrace
> java.lang.RuntimeException: javax.jcr.RepositoryException: Failed to copy
> content
> at
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.prepare(CopyCheckpointsTest.java:141)
> Caused by: javax.jcr.RepositoryException: Failed to copy content
> at
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.prepare(CopyCheckpointsTest.java:141)
> Caused by: java.lang.IllegalArgumentException
> at
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.prepare(CopyCheckpointsTest.java:141)
> {noformat}
> This affects
> {noformat}
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Suppress
> the warning]
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Source
> data store defined, checkpoints migrated]
>
> org.apache.jackrabbit.oak.upgrade.IgnoreMissingBinariesTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.UpgradeOldSegmentTest.upgradeFrom10
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToJdbcTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment-tar -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to embedded, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to external, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to embedded, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to external, src blobstore defined]
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFbsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFdsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FdsToFbsTest.validateMigration
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6513) Journal based Async Indexer
[
https://issues.apache.org/jira/browse/OAK-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6513:
--
Fix Version/s: 1.9.3
> Journal based Async Indexer
> ---
>
> Key: OAK-6513
> URL: https://issues.apache.org/jira/browse/OAK-6513
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Major
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> Current async indexer design is based on NodeState diff. This has served us
> fine so far however off late it is not able to perform well if rate of
> repository writes is high. When changes happen faster than index-update can
> process them, larger and larger diffs will happen. These make index-updates
> slower, which again lead to the next diff being ever larger than the one
> before (assuming a constant ingestion rate).
> In current diff based flow the indexer performs complete diff for all changes
> happening between 2 cycle. It may happen that lots of writes happens but not
> much indexable content is written. So doing diff there is a wasted effort.
> In 1.6 release for NRT Indexing we implemented a journal based indexing for
> external changes(OAK-4808, OAK-5430). That approach can be generalized and
> used for async indexing.
> Before talking about the journal based approach lets see how IndexEditor work
> currently
> h4. IndexEditor
> Currently any IndexEditor performs 2 tasks
> # Identify which node is to be indexed based on some index definition. The
> Editor gets invoked as part of content diff where it determines which
> NodeState is to be indexed
> # Update the index based on node to be indexed
> For e.g. in oak-lucene we have LuceneIndexEditor which identifies the
> NodeStates to be indexed and LuceneDocumentMaker which constructs the Lucene
> Document from NodeState to be indexed. For journal based approach we can
> decouple these 2 parts and thus have
> * IndexEditor - Identifies which all paths need to be indexed for given index
> definition
> * IndexUpdater - Updates the index based on given NodeState and its path
> h4. High Level Flow
> # Session Commit Flow
> ## Each index type would provide a IndexEditor which would be invoked as part
> of commit (like sync indexes). These IndexEditor would just determine which
> paths needs to be indexed.
> ## As part of commit the paths to be indexed would be written to journal.
> # AsyncIndexUpdate flow
> ## AsyncIndexUpdate would query this journal to fetch all such indexed paths
> between the 2 checkpoints
> ## Based on the index path data it would invoke the {{IndexUpdater}} to
> update the index for that path
> ## Merge the index updates
> h4. Benefits
> Such a design would have following impact
> # More work done as part of write
> # Marking of indexable content is distributed hence at indexing time lesser
> work to be done
> # Indexing can progress in batches
> # The indexers can be called in parallel
> h4. Journal Implementation
> DocumentNodeStore currently has an in built journal which is being used for
> NRT Indexing. That feature can be exposed as an api.
> For scaling index this design is mostly required for cluster case. So we can
> possibly have both indexing support implemented and use the journal based
> support for DocumentNodeStore setups. Or we can look into implementing such a
> journal for SegmentNodeStore setups also
> h4. Open Points
> * Journal support in SegmentNodeStore
> * Handling deletes.
> Detailed proposal -
> https://wiki.apache.org/jackrabbit/Journal%20based%20Async%20Indexer
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6914) Improve indexing progress estimates with multiple includes
[ https://issues.apache.org/jira/browse/OAK-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6914: -- Fix Version/s: 1.9.3 > Improve indexing progress estimates with multiple includes > -- > > Key: OAK-6914 > URL: https://issues.apache.org/jira/browse/OAK-6914 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.10, 1.9.2, 1.9.3 > > > With OAK-5970 support was added for providing ETA as indexing progresses. > However as discussed in the issue this estimate might not be good if indexes > have multiple include and excludes > Purpose of this task is to look for ways to improve it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3809) Test failure: FacetTest
[
https://issues.apache.org/jira/browse/OAK-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3809:
--
Fix Version/s: 1.9.3
> Test failure: FacetTest
> ---
>
> Key: OAK-3809
> URL: https://issues.apache.org/jira/browse/OAK-3809
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
> Environment:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
>Reporter: Michael Dürig
>Assignee: Tommaso Teofili
>Priority: Major
> Labels: ci, jenkins, test, test-failure
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> {{org.apache.jackrabbit.oak.jcr.query.FacetTest}} keeps failing on Jenkins:
> {noformat}
> testFacetRetrievalMV(org.apache.jackrabbit.oak.jcr.query.FacetTest) Time
> elapsed: 5.927 sec <<< FAILURE!
> junit.framework.ComparisonFailure: expected: (2), aem (1), apache (1), cosmetics (1), furniture (1)], tags:[repository
> (2), software (2), aem (1), apache (1), cosmetics (1), furniture (1)],
> tags:[repository (2), software (2), aem (1), apache (1), cosmetics (1),
> furniture (1)], tags:[repository (2), software (2), aem (1), apache (1),
> cosmetics (1), furniture (1)]]> but was:
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.jackrabbit.oak.jcr.query.FacetTest.testFacetRetrievalMV(FacetTest.java:80)
> {noformat}
> Failure seen at builds: 628, 629, 630, 633, 634, 636, 642, 643, 644, 645,
> 648, 651, 656, 659, 660, 663, 666
> See e.g.
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/634/#showFailuresLink
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6288) Test failure: upgrade tests failing: Failed to copy content
[
https://issues.apache.org/jira/browse/OAK-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6288:
--
Fix Version/s: 1.9.3
> Test failure: upgrade tests failing: Failed to copy content
> ---
>
> Key: OAK-6288
> URL: https://issues.apache.org/jira/browse/OAK-6288
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, upgrade
>Reporter: Hudson
>Priority: Major
> Labels: CI, jenkins, test-failure
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #364 has failed.
> First failed run: [Jackrabbit Oak
> #364|https://builds.apache.org/job/Jackrabbit%20Oak/364/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/364/console]
> Failing tests:
> {noformat}
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Suppress
> the warning]
>
> org.apache.jackrabbit.oak.upgrade.CopyCheckpointsTest.validateMigration[Source
> data store defined, checkpoints migrated]
>
> org.apache.jackrabbit.oak.upgrade.IgnoreMissingBinariesTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.UpgradeOldSegmentTest.upgradeFrom10
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToJdbcTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTarWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.SegmentToSegmentWithMissingDestinationDirectoryTest.validateMigration
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment-tar -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, no blobstores defined, segment -> segment-tar]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to embedded, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> embedded to external, no blobstores defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> references, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to embedded, src blobstore defined]
>
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.validateMigration[Copy
> external to external, src blobstore defined]
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFbsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FbsToFdsTest.validateMigration
> org.apache.jackrabbit.oak.upgrade.cli.blob.FdsToFbsTest.validateMigration
> {noformat}
> All seem to fail with
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.737
> s <<< FAILURE! - in
> org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest
> [ERROR]
> validateMigration(org.apache.jackrabbit.oak.upgrade.cli.SegmentTarToSegmentTest)
> Time elapsed: 3.73 s <<< ERROR!
> java.lang.RuntimeException: javax.jcr.RepositoryException: Failed to copy
> content
> Caused by: javax.jcr.RepositoryException: Failed to copy content
> Caused by: java.lang.IllegalArgumentException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7074) Ensure that all Documents are read with document order traversal indexing
[ https://issues.apache.org/jira/browse/OAK-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-7074: -- Fix Version/s: 1.9.3 > Ensure that all Documents are read with document order traversal indexing > - > > Key: OAK-7074 > URL: https://issues.apache.org/jira/browse/OAK-7074 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: mongomk, run >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Major > Fix For: 1.10, 1.9.2, 1.9.3 > > > With OAK-6353 support was added for document order traversal indexing. In > this mode we open a DB cursor and try to read all documents from it using > document order traversal. Such a cursor may remain open for long time (2-4 > hrs) and its possible that document may get reordered by the Mongo storage > engine. This would result in 2 aspects to be thought about > # Duplicate documents - Same document may appear more than once in result set > # Possibly missed document - It may be a possibility that a document got > moved and missed becoming part of cursor. > Both these aspects would need to be handled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6062) Test failure: CopyBinariesTest.validateMigration
[
https://issues.apache.org/jira/browse/OAK-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6062:
--
Fix Version/s: 1.9.3
> Test failure: CopyBinariesTest.validateMigration
>
>
> Key: OAK-6062
> URL: https://issues.apache.org/jira/browse/OAK-6062
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, documentmk
>Reporter: Hudson
>Priority: Major
> Labels: CI, flaky-test, jenkins, test-failure
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/
> The build Jackrabbit Oak #146 has failed.
> First failed run: [Jackrabbit Oak
> #146|https://builds.apache.org/job/Jackrabbit%20Oak/146/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/146/console]
> The test failure is:
> {noformat}
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest
> validateMigration[Copy references, no blobstores defined, document ->
> segment-tar](org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest)
> Time elapsed: 2.534 sec <<< ERROR!
> javax.jcr.RepositoryException: Failed to copy content
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> Caused by: java.lang.IllegalStateException: Branch with failed reset
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakOak0100:
> Branch reset failed
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> Caused by: org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> Empty branch cannot be reset
> at
> org.apache.jackrabbit.oak.upgrade.cli.blob.CopyBinariesTest.prepare(CopyBinariesTest.java:183)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6166) Support versioning in the federated node store
[ https://issues.apache.org/jira/browse/OAK-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6166: -- Fix Version/s: 1.9.3 > Support versioning in the federated node store > -- > > Key: OAK-6166 > URL: https://issues.apache.org/jira/browse/OAK-6166 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: composite >Reporter: Tomek Rękawek >Priority: Minor > Fix For: 1.10, 1.9.2, 1.9.3 > > > The mount info provider should affect the versioning code as well, so version > histories for the mounted paths are stored separately. Similarly to what we > have in the indexing, let's store the mounted version histories under: > /jcr:system/jcr:versionStorage/:oak:mount-MOUNTNAME -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7263) oak-lucene should not depend on oak-store-document
[
https://issues.apache.org/jira/browse/OAK-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-7263:
--
Fix Version/s: 1.9.3
> oak-lucene should not depend on oak-store-document
> --
>
> Key: OAK-7263
> URL: https://issues.apache.org/jira/browse/OAK-7263
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> {{oak-lucene}} has a hard dependency on {{oak-store-document}} and that looks
> wrong to me.
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project oak-lucene: Compilation failure: Compilation
> failure:
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneDocumentHolder.java:[31,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneDocumentHolder.java:[37,46]
> cannot find symbol
> [ERROR] symbol: class JournalProperty
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[33,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[34,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[38,47]
> cannot find symbol
> [ERROR] symbol: class JournalPropertyBuilder
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[106,12]
> cannot find symbol
> [ERROR] symbol: class JournalProperty
> [ERROR] location: class
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.LuceneJournalPropertyBuilder
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/LuceneIndexProviderService.java:[55,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/IndexedPaths.java:[29,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/IndexedPaths.java:[33,31]
> cannot find symbol
> [ERROR] symbol: class JournalProperty
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[22,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[23,54]
> package org.apache.jackrabbit.oak.plugins.document.spi does not exist
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[25,54]
> cannot find symbol
> [ERROR] symbol: class JournalPropertyService
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyService.java:[33,12]
> cannot find symbol
> [ERROR] symbol: class JournalPropertyBuilder
> [ERROR] location: class
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.LuceneJournalPropertyService
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[50,5]
> method does not override or implement a method from a supertype
> [ERROR]
> /home/robert/Documents/sources/apache/jackrabbit-oak/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/hybrid/LuceneJournalPropertyBuilder.java:[61,5]
> method does not override or implement a method from a supertype
> [ERROR]
>
[jira] [Updated] (OAK-5544) Improve indexing resilience
[ https://issues.apache.org/jira/browse/OAK-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5544: -- Fix Version/s: 1.9.3 > Improve indexing resilience > --- > > Key: OAK-5544 > URL: https://issues.apache.org/jira/browse/OAK-5544 > Project: Jackrabbit Oak > Issue Type: Epic > Components: lucene >Reporter: Alexander Saar >Assignee: Chetan Mehrotra >Priority: Critical > Labels: resilience > Fix For: 1.10, 1.9.2, 1.9.3 > > > grouping the improvements for indexer resilience in this issue for easier > tracking -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7459) oak-run compact should support Azure Segment Store
[
https://issues.apache.org/jira/browse/OAK-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-7459:
--
Fix Version/s: 1.9.3
> oak-run compact should support Azure Segment Store
> --
>
> Key: OAK-7459
> URL: https://issues.apache.org/jira/browse/OAK-7459
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
> Labels: tooling
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> {{oak-run compact}} should accept Azure URIs for the segment store in order
> to enable OffRC for Azure Segment Store. Proposed options to add:
> * {{azure-connection}}: connection URL to to connect to the Azure Storage
> * {{azure-container}}: name of the container to use
> * {{azure-root-path}}: segment store directory
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-5776) Build failure: Cannot create directory : Filename too long
[ https://issues.apache.org/jira/browse/OAK-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5776: -- Fix Version/s: 1.9.3 > Build failure: Cannot create directory : Filename too long > -- > > Key: OAK-5776 > URL: https://issues.apache.org/jira/browse/OAK-5776 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > Labels: CI, build-failure, test-failure, windows > Fix For: 1.10, 1.9.2, 1.9.3 > > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) > 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #473 > has failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited > security) 64-bit Windows > only,nsfixtures=DOCUMENT_NS,profile=integrationTesting > #473|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=integrationTesting/473/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=integrationTesting/473/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3437) Regression in org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5 when enabling OAK-1617
[
https://issues.apache.org/jira/browse/OAK-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3437:
--
Fix Version/s: 1.9.3
> Regression in org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5 when
> enabling OAK-1617
> --
>
> Key: OAK-3437
> URL: https://issues.apache.org/jira/browse/OAK-3437
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
>Reporter: Davide Giannella
>Assignee: Tommaso Teofili
>Priority: Major
> Fix For: 1.10, 1.9.2, 1.9.3
>
>
> When enabling OAK-1617 (still to be committed) there's a regression in the
> {{oak-solr-core}} unit tests
> - {{org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR3}}
> - {{org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR4}}
> - {{org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5}}
> The WIP of the feature can be found in
> https://github.com/davidegiannella/jackrabbit-oak/tree/OAK-1617 and a full
> patch will be attached shortly for review in OAK-1617 itself.
> The feature is currently disabled, in order to enable it for unit testing an
> approach like this can be taken
> https://github.com/davidegiannella/jackrabbit-oak/blob/177df1a8073b1237857267e23d12a433e3d890a4/oak-core/src/test/java/org/apache/jackrabbit/oak/query/SQL2OptimiseQueryTest.java#L142
> or setting the system property {{-Doak.query.sql2optimisation}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-4524) LucenePropertyIndexTest#longRepExcerpt sometimes failing
[ https://issues.apache.org/jira/browse/OAK-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-4524: -- Fix Version/s: 1.9.3 > LucenePropertyIndexTest#longRepExcerpt sometimes failing > > > Key: OAK-4524 > URL: https://issues.apache.org/jira/browse/OAK-4524 > Project: Jackrabbit Oak > Issue Type: Test > Components: lucene >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > Fix For: 1.10, 1.9.2, 1.9.3 > > > As reported by Julian on oak-dev@ it seems _longRepExcerpt_ is still failing > sometimes when query takes more than 10s e.g. see this [Jenkins > failure|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1000/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.plugins.index.lucene/LucenePropertyIndexTest/longRepExcerpt/]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
