[jira] [Created] (OAK-5713) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1434 failed
Hudson created OAK-5713: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1434 failed Key: OAK-5713 URL: https://issues.apache.org/jira/browse/OAK-5713 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1434 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1434|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1434/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1434/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5711) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1434 failed
Hudson created OAK-5711: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1434 failed Key: OAK-5711 URL: https://issues.apache.org/jira/browse/OAK-5711 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1434 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1434|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1434/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1434/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5712) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1434 failed
Hudson created OAK-5712: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1434 failed Key: OAK-5712 URL: https://issues.apache.org/jira/browse/OAK-5712 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1434 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1434|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1434/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1434/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5710) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1434 failed
Hudson created OAK-5710: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1434 failed Key: OAK-5710 URL: https://issues.apache.org/jira/browse/OAK-5710 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1434 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1434|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=unittesting/1434/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=unittesting/1434/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5709) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1434 failed
Hudson created OAK-5709: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1434 failed Key: OAK-5709 URL: https://issues.apache.org/jira/browse/OAK-5709 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1434 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1434|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1434/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1434/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5608) Test failure: org.apache.jackrabbit.mk.util.CommitGateIT.test
[ https://issues.apache.org/jira/browse/OAK-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872615#comment-15872615 ] Hudson commented on OAK-5608: - Previously failing build now is OK. Passed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=integrationTesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/460/] [console log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/460/console] > Test failure: org.apache.jackrabbit.mk.util.CommitGateIT.test > - > > Key: OAK-5608 > URL: https://issues.apache.org/jira/browse/OAK-5608 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Affects Versions: 1.0.36, 1.2.23 >Reporter: Hudson >Assignee: Marcel Reutegger > Labels: test-failure, windows > Fix For: 1.0.37, 1.2.24 > > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) > 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=integrationTesting #443 > has failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited > security) 64-bit Windows > only,nsfixtures=SEGMENT_TAR,profile=integrationTesting > #443|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/443/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/443/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5639) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #449 failed
[ https://issues.apache.org/jira/browse/OAK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872607#comment-15872607 ] Hudson commented on OAK-5639: - Previously failing build now is OK. Passed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/460/] [console log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/460/console] > Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit > Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #449 failed > > > Key: OAK-5639 > URL: https://issues.apache.org/jira/browse/OAK-5639 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) > 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #449 has > failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited > security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting > #449|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/449/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_NS,profile=unittesting/449/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5694) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_MK,profile=integrationTesting #457 failed
[ https://issues.apache.org/jira/browse/OAK-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872585#comment-15872585 ] Hudson commented on OAK-5694: - Previously failing build now is OK. Passed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_MK,profile=integrationTesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_MK,profile=integrationTesting/460/] [console log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_MK,profile=integrationTesting/460/console] > Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit > Windows only,nsfixtures=SEGMENT_MK,profile=integrationTesting #457 failed > -- > > Key: OAK-5694 > URL: https://issues.apache.org/jira/browse/OAK-5694 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > 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=SEGMENT_MK,profile=integrationTesting #457 has > failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited > security) 64-bit Windows > only,nsfixtures=SEGMENT_MK,profile=integrationTesting > #457|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_MK,profile=integrationTesting/457/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_MK,profile=integrationTesting/457/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5696) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #458 failed
[ https://issues.apache.org/jira/browse/OAK-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872541#comment-15872541 ] Hudson commented on OAK-5696: - Previously failing build now is OK. Passed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=unittesting/460/] [console log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=unittesting/460/console] > Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit > Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #458 failed > - > > Key: OAK-5696 > URL: https://issues.apache.org/jira/browse/OAK-5696 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) > 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #458 has > failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited > security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting > #458|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=unittesting/458/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=unittesting/458/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5708) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=integrationTesting #460 failed
Hudson created OAK-5708: --- Summary: Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=integrationTesting #460 failed Key: OAK-5708 URL: https://issues.apache.org/jira/browse/OAK-5708 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson 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_RDB,profile=integrationTesting #460 has failed. First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=integrationTesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=integrationTesting/460/] [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_RDB,profile=integrationTesting/460/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (OAK-5707) [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, analyzed
[ https://issues.apache.org/jira/browse/OAK-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872536#comment-15872536 ] David Gonzalez edited comment on OAK-5707 at 2/17/17 9:16 PM: -- Including helpful offline conversations w/ Vikas. The following require review for correctness, and are added here to help shape the discussion and for convenience and should NOT be considered correct until the review has been finalized. * Aggregate instruct Oak to fulltext-index any property found under the provided path pattern (ex. */*/*) (avoiding complication of how it recurses through types... ) ** By default all String and String[] properties are candidates for aggregation, however other property types can be specified at the aggregation level. * Specific property index definitions defined under indexRules, are about "how to index a specific property" ** The effected property is defined via a) a relative property path or b) via a regex property path match from the the indexRules applies to. * A property that can be reached by an aggregate rule pattern is same as that property having a `indexRules//properties/myProp@nodeScopeIndex=true` ** The advantages of ALSO defining an indexRule for a property covered by an aggregate are: *** The property can also be marked as a propertyIndex which allows for more performation property based equality matches *** The property can be marked for special use (ex. useInSuggest, useInSpellecheck, boost, etc.) which may (depending on the applied special use properties) how it behaves in the aggregated search. * `analyzed=true` in an indexRules prop def (say for `jcr:content/jcr:title`) allows for `...FROM [app:Page] where CONTAINS([jcr:content/jcr:title], 'foo')` ** TBD what special user props are applicable to this (if any?) * 'propertyIndex=true` is for the condition you were asking at first `WHERE [jcr:content/jcr:title]='foo'` ** If the property is a candidate for aggregates or nodeScopeIndex (which as noted are ~ equivalent), equality property conditions (WHERE [jcr:content/jcr:title]='foo') may still appear fast and not report a traversal warning, as Oak is able to leverage the internal aggregate index to quickly isolate matches. That being said, for property equality checks, it is always as fast (if not faster) to defined an indexRule for the property with `propertyIndex=true` ** TBD clearly describe the considerations of equality matches when only using the aggregate index. * aggregate and nodeScopeIndex are intended to roll content up into the index's "nodeType" index, so that content will be candidate for fulltext searchs against that node (vs against a specific property) or rather: `WHERE CONTAINS(*, 'foo')` * The `excludeFromAggregation` prop "disables" aggregate indexing of a prop that matches a prop def having `excludeFromAggregation` was (Author: empire29): Including helpful offline conversations w/ Vikas. The following require review for correctness, and are added here to help shape the discussion and for convenience. * Aggregate instruct Oak to fulltext-index any property found under the provided path pattern (ex. */*/*) (avoiding complication of how it recurses through types... ) ** By default all String and String[] properties are candidates for aggregation, however other property types can be specified at the aggregation level. * Specific property index definitions defined under indexRules, are about "how to index a specific property" ** The effected property is defined via a) a relative property path or b) via a regex property path match from the the indexRules applies to. * A property that can be reached by an aggregate rule pattern is same as that property having a `indexRules//properties/myProp@nodeScopeIndex=true` ** The advantages of ALSO defining an indexRule for a property covered by an aggregate are: *** The property can also be marked as a propertyIndex which allows for more performation property based equality matches *** The property can be marked for special use (ex. useInSuggest, useInSpellecheck, boost, etc.) which may (depending on the applied special use properties) how it behaves in the aggregated search. * `analyzed=true` in an indexRules prop def (say for `jcr:content/jcr:title`) allows for `...FROM [app:Page] where CONTAINS([jcr:content/jcr:title], 'foo')` ** TBD what special user props are applicable to this (if any?) * 'propertyIndex=true` is for the condition you were asking at first `WHERE [jcr:content/jcr:title]='foo'` ** If the property is a candidate for aggregates or nodeScopeIndex (which as noted are ~ equivalent), equality property conditions (WHERE [jcr:content/jcr:title]='foo') may still appear fast and not report a traversal warning, as Oak is able to leverage the internal aggregate index to quickly isolate matches. That being said, for property equality checks, it is always as
[jira] [Commented] (OAK-5693) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #457 failed
[ https://issues.apache.org/jira/browse/OAK-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872527#comment-15872527 ] Hudson commented on OAK-5693: - Previously failing build now is OK. Passed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=unittesting/460/] [console log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=unittesting/460/console] > Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit > Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #457 failed > > > Key: OAK-5693 > URL: https://issues.apache.org/jira/browse/OAK-5693 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > 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=SEGMENT_TAR,profile=unittesting #457 has > failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited > security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting > #457|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=unittesting/457/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=unittesting/457/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OAK-5707) [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, analyzed
[ https://issues.apache.org/jira/browse/OAK-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Saurabh reassigned OAK-5707: -- Assignee: Vikas Saurabh > [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, > analyzed > > > Key: OAK-5707 > URL: https://issues.apache.org/jira/browse/OAK-5707 > Project: Jackrabbit Oak > Issue Type: Documentation >Reporter: David Gonzalez >Assignee: Vikas Saurabh > > Oak lucene documentation would benefit from clarifying the relationships and > expect behaviors around aggregates, nodeScopeIndex, propertyIndex and > analyzed. > These features have some overlap in what they do and/or augment one another, > but to the lay-developer it is unclear how these work in concern and/or the > implications of these using the various features. > Its worth remembering many developers are under the mindset (shifting from > jackrabbit 2 -> oak) that oak indexing requires explicit inclusion of content > into search results; thus implicit content inclusion into indexes via > generalized aggregations (vs named properties) is unclear/unexpected to many. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull
[ https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872509#comment-15872509 ] Hudson commented on OAK-5668: - Previously failing build now is OK. Passed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #460|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=unittesting/460/] [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_RDB,profile=unittesting/460/console] > Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull > -- > > Key: OAK-5668 > URL: https://issues.apache.org/jira/browse/OAK-5668 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration, jcr >Affects Versions: 1.2.23, 1.4.13 >Reporter: Hudson > Labels: test-failure, ubuntu, windows > Fix For: 1.2.24, 1.4.15, 1.7.0, 1.8, 1.6.1 > > Attachments: unit-tests.log > > > 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_RDB,profile=unittesting #452 has > failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited > security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting > #452|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.7%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=DOCUMENT_RDB,profile=unittesting/452/] > [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_RDB,profile=unittesting/452/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5707) [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, analyzed
David Gonzalez created OAK-5707: --- Summary: [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, analyzed Key: OAK-5707 URL: https://issues.apache.org/jira/browse/OAK-5707 Project: Jackrabbit Oak Issue Type: Documentation Reporter: David Gonzalez Oak lucene documentation would benefit from clarifying the relationships and expect behaviors around aggregates, nodeScopeIndex, propertyIndex and analyzed. These features have some overlap in what they do and/or augment one another, but to the lay-developer it is unclear how these work in concern and/or the implications of these using the various features. Its worth remembering many developers are under the mindset (shifting from jackrabbit 2 -> oak) that oak indexing requires explicit inclusion of content into search results; thus implicit content inclusion into indexes via generalized aggregations (vs named properties) is unclear/unexpected to many. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations
[
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871971#comment-15871971
]
David Gonzalez commented on OAK-5692:
-
[~chetanm] thanks - this is a treasure trove of information!!!
Do you have any thoughts on the language-based considerations and if that is
possible to handle today in Oak? The 2 main use-case i see are:
* Switching the default language from English (which i believe it is?) to some
other language/locale
* Supporting multiple languages in a single index. For example i have a
app:Page index, but i have app:Pages in english, french, german, spanish -- can
i specify multiple language specific charFilters/tokenizers/filters? If yes,
how and how does the indexing/query know which to invoke?
I will check out updated docs!
> Oak Lucene analyzers docs unclear on viable configurations
> --
>
> Key: OAK-5692
> URL: https://issues.apache.org/jira/browse/OAK-5692
> Project: Jackrabbit Oak
> Issue Type: Documentation
>Reporter: David Gonzalez
>Assignee: Chetan Mehrotra
>
> The Oak lucene docs [1] > Analyzers section would benefit from clarification:
> Combining analyzer-based topics into a single ticket
> * If no analyzer is specified, what analyzer setup is used (at a bare
> minimum, _some_ tokenizer must be used)
> * The docs mention the "default" analyzer
> ([oak:queryIndexDefinition]/analyzers/default).
> ** Can other analyzers be defined?
> ** How are they selected for use?
> ** is the selection configurable?
> * Is the analyzer both index AND query time (unless specified by
> `type=index|query` property)?
> * What is the naming for multiple analyzer nodes? Are all children of
> analyzers assumed to be an analyzer? Ex. If i want a special configuration or
> index and another for query, could i create:
> {noformat}
> ../myIndex/analyzers/indexAnalyzer@type=index
> .. define the index-time analyzer ...
> ../myIndex/analyzers/queryAnalyzer@type=query
> .. define the query-time analyzer ...
> {noformat}
> * How are languages handled? Ex. language specific stop words, synonyms, char
> mapping, and Stemming.
> * If
> [oak:queryIndexDefinition]/analyzers/default@class=org.apache.lucene.analysis.standard.StandardAnalyzer
> it appears the Standard Tokenizer and Standard Lowercase and Stop Filters
> are used. The Stop filter can be augmented w the well-named stopwords file.
> ** Can other charFilters/filters be layered on top of this "named" Analyzer
> (it seems not).
> * When the Stop Filter is used it provided the OOTB language-based stop
> words. If a custom stopwords file is provided, that list replaced the OOTB
> lang-based, requiring the developer to provide their own language based Stop
> words. Is this correct? This should be called out and link out to the catalog
> of OOTB stopword txt files for easy inclusion)
> * The Stop filters words property must be a String not String[] and the value
> is a comma delimited String value. Would be good to call this out.
> * What are all the CharFilters/Filters available? Is there a concise list w/
> their params? (Ex. i think the PorterStem might support and ignoreCase param?)
> * Synonym Filter syntax is unclear; It seems like here are 2 formats;
> directional x -> y and bi-directional (comma delimited); i could only get the
> latter to work.
> * Are all the options in the link [2] supported. Its unclear if there is a
> 1:1 between oak lucene and solr's capabilities or if [2] is a loose example
> of the "types" of supported analyzers.
> * For things something like the PatternReplaceCharFilterFactory [3], how do
> you define multiple pattern mappings, as IIUC the charFilter node MUST be
> named:
> {noformat}.../charFilters/PatternReplace{noformat} so you can't have multiple
> "PatternReplace" named nodes, each with its own "@pattern" and "@replace"
> properties. It seems like there is only support for a single object for each
> Factory type?
> Generally this seems like the handiest resource:
> https://cwiki.apache.org/confluence/display/solr/Understanding+Analyzers%2C+Tokenizers%2C+and+Filters
> [1] http://jackrabbit.apache.org/oak/docs/query/lucene.html
> [2]
> https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#Specifying_an_Analyzer_in_the_schema
> [3] https://cwiki.apache.org/confluence/display/solr/CharFilterFactories
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations
[
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Gonzalez updated OAK-5692:
Description:
The Oak lucene docs [1] > Analyzers section would benefit from clarification:
Combining analyzer-based topics into a single ticket
* If no analyzer is specified, what analyzer setup is used (at a bare minimum,
_some_ tokenizer must be used)
* The docs mention the "default" analyzer
([oak:queryIndexDefinition]/analyzers/default).
** Can other analyzers be defined?
** How are they selected for use?
** is the selection configurable?
* Is the analyzer both index AND query time (unless specified by
`type=index|query` property)?
* What is the naming for multiple analyzer nodes? Are all children of analyzers
assumed to be an analyzer? Ex. If i want a special configuration or index and
another for query, could i create:
{noformat}
../myIndex/analyzers/indexAnalyzer@type=index
.. define the index-time analyzer ...
../myIndex/analyzers/queryAnalyzer@type=query
.. define the query-time analyzer ...
{noformat}
* How are languages handled? Ex. language specific stop words, synonyms, char
mapping, and Stemming.
* If
[oak:queryIndexDefinition]/analyzers/default@class=org.apache.lucene.analysis.standard.StandardAnalyzer
it appears the Standard Tokenizer and Standard Lowercase and Stop Filters are
used. The Stop filter can be augmented w the well-named stopwords file.
** Can other charFilters/filters be layered on top of this "named" Analyzer (it
seems not).
* When the Stop Filter is used it provided the OOTB language-based stop words.
If a custom stopwords file is provided, that list replaced the OOTB lang-based,
requiring the developer to provide their own language based Stop words. Is this
correct? This should be called out and link out to the catalog of OOTB stopword
txt files for easy inclusion)
* The Stop filters words property must be a String not String[] and the value
is a comma delimited String value. Would be good to call this out.
* What are all the CharFilters/Filters available? Is there a concise list w/
their params? (Ex. i think the PorterStem might support and ignoreCase param?)
* Synonym Filter syntax is unclear; It seems like here are 2 formats;
directional x -> y and bi-directional (comma delimited); i could only get the
latter to work.
* Are all the options in the link [2] supported. Its unclear if there is a 1:1
between oak lucene and solr's capabilities or if [2] is a loose example of the
"types" of supported analyzers.
* For things something like the PatternReplaceCharFilterFactory [3], how do you
define multiple pattern mappings, as IIUC the charFilter node MUST be named:
{noformat}.../charFilters/PatternReplace{noformat} so you can't have multiple
"PatternReplace" named nodes, each with its own "@pattern" and "@replace"
properties. It seems like there is only support for a single object for each
Factory type?
Generally this seems like the handiest resource:
https://cwiki.apache.org/confluence/display/solr/Understanding+Analyzers%2C+Tokenizers%2C+and+Filters
[1] http://jackrabbit.apache.org/oak/docs/query/lucene.html
[2]
https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#Specifying_an_Analyzer_in_the_schema
[3] https://cwiki.apache.org/confluence/display/solr/CharFilterFactories
was:
The Oak lucene docs [1] > Analyzers section would benefit from clarification:
Combining analyzer-based topics into a single ticket
* If no analyzer is specified, what analyzer setup is used (at the vert least
some tokenizer must be used)
* The docs mention the "default" analyzer
([oak:queryIndexDefinition]/analyzers/default). Can other analyzers be defined?
How are they selected for use? is the selection configurable?
* By default is the analyzer index AND query time, unless specified by
`type=index|query` property?
* What is the naming for multiple analyzer nodes? Are all children of analyzers
assumed to be an analyzer? Ex. If i want a special configuration or index and
another for query, could i create:
{noformat}
../myIndex/analyzers/indexAnalyzer@type=index
.. define the index-time analyzer ...
../myIndex/analyzers/queryAnalyzer@type=query
.. define the query-time analyzer ...
{noformat}
* How are languages handled? Ex. language specific stop words, synonyms, char
mapping, and Stemming.
* If
[oak:queryIndexDefinition]/analyzers/default@class=org.apache.lucene.analysis.standard.StandardAnalyzer
it appears the Standard Tokenizer and Standard Lowercase and Stop Filters are
used. The Stop filter can be augmented w the well-named stopwords file.
** Can other charFilters/filters be layered on top of this "named" Analyzer (it
seems not).
* When the Stop Filter is used it provided the OOTB language-based stop words.
If a custom stopwords file is provided, that list replaced the OOTB lang-based,
requiring the developer to provide their own language
[jira] [Issue Comment Deleted] (OAK-5571) VersionGarbageCollector can remove leaf nodes eagerly
[ https://issues.apache.org/jira/browse/OAK-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-5571: Comment: was deleted (was: trunk: [r1782008|http://svn.apache.org/r1782008] ) > VersionGarbageCollector can remove leaf nodes eagerly > - > > Key: OAK-5571 > URL: https://issues.apache.org/jira/browse/OAK-5571 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_oak_1_4, candidate_oak_1_6, resilience > Fix For: 1.7.0, 1.8 > > Attachments: clean_leaves.patch, OAK-5571.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5571) VersionGarbageCollector can remove leaf nodes eagerly
[ https://issues.apache.org/jira/browse/OAK-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871964#comment-15871964 ] Julian Reschke commented on OAK-5571: - trunk: [r1783411|http://svn.apache.org/r1783411] [r1782008|http://svn.apache.org/r1782008] > VersionGarbageCollector can remove leaf nodes eagerly > - > > Key: OAK-5571 > URL: https://issues.apache.org/jira/browse/OAK-5571 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_oak_1_4, candidate_oak_1_6, resilience > Fix For: 1.7.0, 1.8 > > Attachments: clean_leaves.patch, OAK-5571.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5706) Function based indexes with "like" conditions
Thomas Mueller created OAK-5706:
---
Summary: Function based indexes with "like" conditions
Key: OAK-5706
URL: https://issues.apache.org/jira/browse/OAK-5706
Project: Jackrabbit Oak
Issue Type: Bug
Reporter: Thomas Mueller
Assignee: Thomas Mueller
Fix For: 1.8
Currently, a function-based index is not used when using "like" conditions, as
follows:
{noformat}
/jcr:root//*[jcr:like(fn:lower-case(fn:name()), 'abc%')]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OAK-3134) Identify functionality offered by oak-run
[ https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871925#comment-15871925 ] Davide Giannella commented on OAK-3134: --- The original point was about size. Deploying 50MB+ at time can be challenging (depending on bandwidth). The investigation in OAK-3766 identified embedded libraries where the biggest part of the jar and by simply removing dependencies it would have cleared the issue. Unfortunately some dependencies are possible to be removed as they're used in "development" stuff like benchmark and scalability. I think this where the "oak-development" and "operations" came from originally. Most probably by simply creating a benchmark module where we put in all the benchmarks and scalability could achieve most of the main goal around size. So we could start by moving in this direction if everyone agrees. Of course benchmark won't be deployed on maven otherwise we're most probably back to square one. with regards to OAK-5437 I think it can be addressed separately. But the original point here was simply about size. A side question still remain: what about backports? If we go for oak-benchmarks; how are we going to deal with backports? > Identify functionality offered by oak-run > - > > Key: OAK-3134 > URL: https://issues.apache.org/jira/browse/OAK-3134 > Project: Jackrabbit Oak > Issue Type: Task > Components: run >Reporter: Davide Giannella >Assignee: Davide Giannella > > oak-run reached the size of 50MB+ and offers indeed various functionalities > that could be moved to their own module. > This ticket is about to identify what oak-run currently offers and what/if > could be split. > ML thread: http://markmail.org/thread/w34bphrk57l7pkaz > || Functionality || Package || Module || > | Backup | | oak-operations| > | Check | | oak-operations| > | Checkpoints | | oak-operations| > | Compact | | oak-operations| > | Debug | | oak-operations| > | Explore | |oak-development | > | Groovy console | org.apache.jackrabbit.oak.console, > /oak-run/src/main/groovy/org/apache/jackrabbit/oak/console | oak-operations| > | Primary | | oak-development| > | Recovery | | oak-operations| > | Repair | | oak-operations| > | Restore | | oak-operations| > | Server | | oak-development| > | Standby | | oak-development| > | Upgrade | | oak-upgrade| > | micro-benchmark | org.apache.jackrabbit.oak.benchmark |oak-development | > | scalability benchmark | org.apache.jackrabbit.oak.scalability | > oak-development| > | DataStoreCacheUpgrade | | oak-operations | > | DataStoreCheck | | oak-operations | > | Garbage | | oak-operations | > | tarmkdiff | | oak-operations | > | tarmkrecovery | | oak-operations | > | graph | | oak-development | > | history | | oak-operations | > | index | | oak-operations | > | persistentcache | | oak-operations | > | resetclusterid | | oak-operations | > | threaddump | | oak-development | > | tika | | oak-operations | > Modules left after the actions: > **oak-development** > Used to group and execute all the tools used during development. > _deployed to maven:_ No. > **oak-operations** > Used to group and execute all the tools used normally in production > environment for tasks like maintenance & C. > _deployed to maven:_ Yes. > **oak-run** > Will group what's left after the split. > _deployed to maven:_ No. > **oak-upgrade** > Will group tools for upgrading/migrating from one repo/version to another > _deployed to maven:_ yes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5705) Negative cost calculation for native Solr query
Tommaso Teofili created OAK-5705:
Summary: Negative cost calculation for native Solr query
Key: OAK-5705
URL: https://issues.apache.org/jira/browse/OAK-5705
Project: Jackrabbit Oak
Issue Type: Bug
Components: solr
Affects Versions: 1.6.0
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Fix For: 1.7.0
It seems sometimes the cost for the Solr index can become negative.
This has been observed specifically with native queries, as witnessed by log
lines like
{noformat}
org.apache.jackrabbit.oak.query.QueryImpl cost below 0 for
solr[/oak:index/solrIndex] is -2.7670116110564326E18
{noformat}
A sample query causing this :
{noformat}
select * from [nt:base] where native('solr','select?q=searchKeywords:"foo"^20
text:"foo"^1 searchExcerpt:"foo"^8 subheadline:"foo"^3 headline:"foo"^5
searchHeadline:"foo"^10 =OR'
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (OAK-5703) The replica set info gets invalid cluster id
[ https://issues.apache.org/jira/browse/OAK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek resolved OAK-5703. Resolution: Fixed > The replica set info gets invalid cluster id > > > Key: OAK-5703 > URL: https://issues.apache.org/jira/browse/OAK-5703 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, mongomk >Affects Versions: 1.6.0 >Reporter: Tomek Rękawek > Fix For: 1.7.0, 1.8 > > Attachments: OAK-5703.patch > > > A part of the replica set info provider (namely, the LocalChanges), uses the > instance cluster id to find out whether Oak is being run in cluster. > However, the way in which MongoDocumentStore provides this clusterId to the > LocalChanges class is not correct. It's taken from the DocumentMK.Builder, > which works only for the case when it's being set explicitly in the > configuration and doesn't work if Oak gets its clusterId automatically. > As a result, if the clusterId isn't set in the configuration, the > LocalChanges class remains disabled and doesn't allow to use the secondary > Mongo instances for find() and query() requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5703) The replica set info gets invalid cluster id
[ https://issues.apache.org/jira/browse/OAK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871900#comment-15871900 ] Tomek Rękawek commented on OAK-5703: Fixed for trunk in [r1783406|https://svn.apache.org/r1783406]. > The replica set info gets invalid cluster id > > > Key: OAK-5703 > URL: https://issues.apache.org/jira/browse/OAK-5703 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, mongomk >Affects Versions: 1.6.0 >Reporter: Tomek Rękawek > Fix For: 1.7.0, 1.8 > > Attachments: OAK-5703.patch > > > A part of the replica set info provider (namely, the LocalChanges), uses the > instance cluster id to find out whether Oak is being run in cluster. > However, the way in which MongoDocumentStore provides this clusterId to the > LocalChanges class is not correct. It's taken from the DocumentMK.Builder, > which works only for the case when it's being set explicitly in the > configuration and doesn't work if Oak gets its clusterId automatically. > As a result, if the clusterId isn't set in the configuration, the > LocalChanges class remains disabled and doesn't allow to use the secondary > Mongo instances for find() and query() requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5704) VersionGC: reset _deletedOnce for documents that have been resurrected
[ https://issues.apache.org/jira/browse/OAK-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-5704: Attachment: OAK-5704.diff Proposed patch. > VersionGC: reset _deletedOnce for documents that have been resurrected > -- > > Key: OAK-5704 > URL: https://issues.apache.org/jira/browse/OAK-5704 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Attachments: OAK-5704.diff > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5703) The replica set info gets invalid cluster id
[ https://issues.apache.org/jira/browse/OAK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated OAK-5703: --- Fix Version/s: 1.8 1.7.0 > The replica set info gets invalid cluster id > > > Key: OAK-5703 > URL: https://issues.apache.org/jira/browse/OAK-5703 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, mongomk >Affects Versions: 1.6.0 >Reporter: Tomek Rękawek > Fix For: 1.7.0, 1.8 > > Attachments: OAK-5703.patch > > > A part of the replica set info provider (namely, the LocalChanges), uses the > instance cluster id to find out whether Oak is being run in cluster. > However, the way in which MongoDocumentStore provides this clusterId to the > LocalChanges class is not correct. It's taken from the DocumentMK.Builder, > which works only for the case when it's being set explicitly in the > configuration and doesn't work if Oak gets its clusterId automatically. > As a result, if the clusterId isn't set in the configuration, the > LocalChanges class remains disabled and doesn't allow to use the secondary > Mongo instances for find() and query() requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-5703) The replica set info gets invalid cluster id
[ https://issues.apache.org/jira/browse/OAK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871861#comment-15871861 ] Tomek Rękawek commented on OAK-5703: Patch attached. In postpones the LocalChanges initialization until we have the true cluster id. In order to get the cluster id, the RevisionListener interface was modified to include the clusterId in the updateAccessedRevision() method. That's why all the other DocumentStore wrappers had to be updated as well. > The replica set info gets invalid cluster id > > > Key: OAK-5703 > URL: https://issues.apache.org/jira/browse/OAK-5703 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, mongomk >Affects Versions: 1.6.0 >Reporter: Tomek Rękawek > Attachments: OAK-5703.patch > > > A part of the replica set info provider (namely, the LocalChanges), uses the > instance cluster id to find out whether Oak is being run in cluster. > However, the way in which MongoDocumentStore provides this clusterId to the > LocalChanges class is not correct. It's taken from the DocumentMK.Builder, > which works only for the case when it's being set explicitly in the > configuration and doesn't work if Oak gets its clusterId automatically. > As a result, if the clusterId isn't set in the configuration, the > LocalChanges class remains disabled and doesn't allow to use the secondary > Mongo instances for find() and query() requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5703) The replica set info gets invalid cluster id
[ https://issues.apache.org/jira/browse/OAK-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated OAK-5703: --- Attachment: OAK-5703.patch > The replica set info gets invalid cluster id > > > Key: OAK-5703 > URL: https://issues.apache.org/jira/browse/OAK-5703 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, mongomk >Affects Versions: 1.6.0 >Reporter: Tomek Rękawek > Attachments: OAK-5703.patch > > > A part of the replica set info provider (namely, the LocalChanges), uses the > instance cluster id to find out whether Oak is being run in cluster. > However, the way in which MongoDocumentStore provides this clusterId to the > LocalChanges class is not correct. It's taken from the DocumentMK.Builder, > which works only for the case when it's being set explicitly in the > configuration and doesn't work if Oak gets its clusterId automatically. > As a result, if the clusterId isn't set in the configuration, the > LocalChanges class remains disabled and doesn't allow to use the secondary > Mongo instances for find() and query() requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5571) VersionGarbageCollector can remove leaf nodes eagerly
[ https://issues.apache.org/jira/browse/OAK-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Eissing updated OAK-5571: Attachment: clean_leaves.patch Patch that clears the leaves collection after batch remove. > VersionGarbageCollector can remove leaf nodes eagerly > - > > Key: OAK-5571 > URL: https://issues.apache.org/jira/browse/OAK-5571 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_oak_1_4, candidate_oak_1_6, resilience > Fix For: 1.7.0, 1.8 > > Attachments: clean_leaves.patch, OAK-5571.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5704) VersionGC: reset _deletedOnce for documents that have been resurrected
Julian Reschke created OAK-5704: --- Summary: VersionGC: reset _deletedOnce for documents that have been resurrected Key: OAK-5704 URL: https://issues.apache.org/jira/browse/OAK-5704 Project: Jackrabbit Oak Issue Type: Improvement Components: documentmk Reporter: Julian Reschke Assignee: Julian Reschke Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (OAK-5571) VersionGarbageCollector can remove leaf nodes eagerly
[ https://issues.apache.org/jira/browse/OAK-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reopened OAK-5571: - After executing a delete batch, the List containing the ids needs to be reset. > VersionGarbageCollector can remove leaf nodes eagerly > - > > Key: OAK-5571 > URL: https://issues.apache.org/jira/browse/OAK-5571 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_oak_1_4, candidate_oak_1_6, resilience > Fix For: 1.7.0, 1.8 > > Attachments: OAK-5571.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5703) The replica set info gets invalid cluster id
Tomek Rękawek created OAK-5703: -- Summary: The replica set info gets invalid cluster id Key: OAK-5703 URL: https://issues.apache.org/jira/browse/OAK-5703 Project: Jackrabbit Oak Issue Type: Bug Components: core, mongomk Affects Versions: 1.6.0 Reporter: Tomek Rękawek A part of the replica set info provider (namely, the LocalChanges), uses the instance cluster id to find out whether Oak is being run in cluster. However, the way in which MongoDocumentStore provides this clusterId to the LocalChanges class is not correct. It's taken from the DocumentMK.Builder, which works only for the case when it's being set explicitly in the configuration and doesn't work if Oak gets its clusterId automatically. As a result, if the clusterId isn't set in the configuration, the LocalChanges class remains disabled and doesn't allow to use the secondary Mongo instances for find() and query() requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5702) Update Felix JAAS to 1.0.2
[ https://issues.apache.org/jira/browse/OAK-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-5702: - Priority: Minor (was: Major) > Update Felix JAAS to 1.0.2 > -- > > Key: OAK-5702 > URL: https://issues.apache.org/jira/browse/OAK-5702 > Project: Jackrabbit Oak > Issue Type: Task > Components: auth-external, exercise, parent, pojosr >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.7.0, 1.8 > > > Felix JAAS 1.0.2 is released which fixes some race condition bugs. We should > update the build to use that -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OAK-5702) Update Felix JAAS to 1.0.2
[ https://issues.apache.org/jira/browse/OAK-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved OAK-5702. -- Resolution: Fixed Done in 1783373 > Update Felix JAAS to 1.0.2 > -- > > Key: OAK-5702 > URL: https://issues.apache.org/jira/browse/OAK-5702 > Project: Jackrabbit Oak > Issue Type: Task > Components: auth-external, exercise, parent, pojosr >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.7.0, 1.8 > > > Felix JAAS 1.0.2 is released which fixes some race condition bugs. We should > update the build to use that -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OAK-5702) Update Felix JAAS to 1.0.2
Chetan Mehrotra created OAK-5702: Summary: Update Felix JAAS to 1.0.2 Key: OAK-5702 URL: https://issues.apache.org/jira/browse/OAK-5702 Project: Jackrabbit Oak Issue Type: Task Components: auth-external, exercise, parent, pojosr Reporter: Chetan Mehrotra Assignee: Chetan Mehrotra Fix For: 1.7.0, 1.8 Felix JAAS 1.0.2 is released which fixes some race condition bugs. We should update the build to use that -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-4780) VersionGarbageCollector should be able to run incrementally
[
https://issues.apache.org/jira/browse/OAK-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871632#comment-15871632
]
Julian Reschke commented on OAK-4780:
-
To cover the case of a VGC that has never run, or one that hasn't run for a
long time, we'll need a way to constrain the scope of the scan to a smaller
time window.
One method would be, as previously proposed, to time-box the collection phase,
to track the lastmod range upon reaching the limit, to give up and try with a
smaller time window.
An alternative might be to extend the {{VersionGCSupport}} even more and to
allow just returning the *count* of candidate nodes. With that information, we
might be able to shrink the time window of the candidate scan *before* actually
trying to collect the nodes.
> VersionGarbageCollector should be able to run incrementally
> ---
>
> Key: OAK-4780
> URL: https://issues.apache.org/jira/browse/OAK-4780
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core, documentmk
>Reporter: Julian Reschke
> Attachments: leafnodes.diff, leafnodes-v2.diff, leafnodes-v3.diff
>
>
> Right now, the documentmk's version garbage collection runs in several phases.
> It first collects the paths of candidate nodes, and only once this has been
> successfully finished, starts actually deleting nodes.
> This can be a problem when the regularly scheduled garbage collection is
> interrupted during the path collection phase, maybe due to other maintenance
> tasks. On the next run, the number of paths to be collected will be even
> bigger, thus making it even more likely to fail.
> We should think about a change in the logic that would allow the GC to run in
> chunks; maybe by partitioning the path space by top level directory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OAK-4780) VersionGarbageCollector should be able to run incrementally
[ https://issues.apache.org/jira/browse/OAK-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871594#comment-15871594 ] Julian Reschke commented on OAK-4780: - [~stefan.eissing] - OAK-5571 improves the situation, but IMHO doesn't completely reach the goal. Optimally, the version GC will "eventually" be able to complete garbage collection, no matter for how long it did not run before. > VersionGarbageCollector should be able to run incrementally > --- > > Key: OAK-4780 > URL: https://issues.apache.org/jira/browse/OAK-4780 > Project: Jackrabbit Oak > Issue Type: Task > Components: core, documentmk >Reporter: Julian Reschke > Attachments: leafnodes.diff, leafnodes-v2.diff, leafnodes-v3.diff > > > Right now, the documentmk's version garbage collection runs in several phases. > It first collects the paths of candidate nodes, and only once this has been > successfully finished, starts actually deleting nodes. > This can be a problem when the regularly scheduled garbage collection is > interrupted during the path collection phase, maybe due to other maintenance > tasks. On the next run, the number of paths to be collected will be even > bigger, thus making it even more likely to fail. > We should think about a change in the logic that would allow the GC to run in > chunks; maybe by partitioning the path space by top level directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Moved] (OAK-5701) Update Oak 1.0 to Jackrabbit 2.8.5
[ https://issues.apache.org/jira/browse/OAK-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke moved JCR-4114 to OAK-5701: -- Component/s: (was: parent) parent Workflow: no-reopen-closed (was: no-reopen-closed, patch-avail) Key: OAK-5701 (was: JCR-4114) Project: Jackrabbit Oak (was: Jackrabbit Content Repository) > Update Oak 1.0 to Jackrabbit 2.8.5 > -- > > Key: OAK-5701 > URL: https://issues.apache.org/jira/browse/OAK-5701 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-4780) VersionGarbageCollector should be able to run incrementally
[ https://issues.apache.org/jira/browse/OAK-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871558#comment-15871558 ] Stefan Eissing commented on OAK-4780: - [~reschke] With OAK-5571 committed in trunk, this one can be closed, right? > VersionGarbageCollector should be able to run incrementally > --- > > Key: OAK-4780 > URL: https://issues.apache.org/jira/browse/OAK-4780 > Project: Jackrabbit Oak > Issue Type: Task > Components: core, documentmk >Reporter: Julian Reschke > Attachments: leafnodes.diff, leafnodes-v2.diff, leafnodes-v3.diff > > > Right now, the documentmk's version garbage collection runs in several phases. > It first collects the paths of candidate nodes, and only once this has been > successfully finished, starts actually deleting nodes. > This can be a problem when the regularly scheduled garbage collection is > interrupted during the path collection phase, maybe due to other maintenance > tasks. On the next run, the number of paths to be collected will be even > bigger, thus making it even more likely to fail. > We should think about a change in the logic that would allow the GC to run in > chunks; maybe by partitioning the path space by top level directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5633) Builds on travis-ci time out
[ https://issues.apache.org/jira/browse/OAK-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-5633: - Component/s: continuous integration > Builds on travis-ci time out > > > Key: OAK-5633 > URL: https://issues.apache.org/jira/browse/OAK-5633 > Project: Jackrabbit Oak > Issue Type: Test > Components: continuous integration, core, documentmk >Affects Versions: 1.6.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.8, 1.6.1 > > > Recent builds on travis-ci time out frequently because they hit the 50 > minutes build time limit. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5633) Builds on travis-ci time out
[ https://issues.apache.org/jira/browse/OAK-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-5633: - Labels: (was: continuous_integration) > Builds on travis-ci time out > > > Key: OAK-5633 > URL: https://issues.apache.org/jira/browse/OAK-5633 > Project: Jackrabbit Oak > Issue Type: Test > Components: continuous integration, core, documentmk >Affects Versions: 1.6.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.8, 1.6.1 > > > Recent builds on travis-ci time out frequently because they hit the 50 > minutes build time limit. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (OAK-5534) Build timed out
[
https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871404#comment-15871404
]
Alex Parvulescu edited comment on OAK-5534 at 2/17/17 8:29 AM:
---
attached log from failing build 1432. seems both segment and document rdb jobs
failed with a timeout.
{noformat}
[integrationTesting] $ /home/jenkins/tools/maven/apache-maven-3.2.1/bin/mvn
"-Djdk=JDK 1.8 (latest)" -Dprofile=integrationTesting "-DUbuntu Slaves=ubuntu"
-Dnsfixtures=DOCUMENT_RDB clean verify -PintegrationTesting
-Dstandby.test.timeout=5000 -Dsurefire.skip.ut=true -Dmongo.port=9
-Prdb-derby -DREMOVEMErdb.jdbc-url=jdbc:derby:oaktest\;create=true
{noformat}
{noformat}
[integrationTesting] $ /home/jenkins/tools/maven/apache-maven-3.2.1/bin/mvn
"-Djdk=JDK 1.8 (latest)" -Dprofile=integrationTesting "-DUbuntu Slaves=ubuntu"
-Dnsfixtures=SEGMENT_TAR clean verify -PintegrationTesting
-Dstandby.test.timeout=5000 -Dsurefire.skip.ut=true -Dmongo.port=9
-Prdb-derby -DREMOVEMErdb.jdbc-url=jdbc:derby:oaktest\;create=true
{noformat}
was (Author: alex.parvulescu):
attached log from failing build 1432
{noformat}
[integrationTesting] $ /home/jenkins/tools/maven/apache-maven-3.2.1/bin/mvn
"-Djdk=JDK 1.8 (latest)" -Dprofile=integrationTesting "-DUbuntu Slaves=ubuntu"
-Dnsfixtures=DOCUMENT_RDB clean verify -PintegrationTesting
-Dstandby.test.timeout=5000 -Dsurefire.skip.ut=true -Dmongo.port=9
-Prdb-derby -DREMOVEMErdb.jdbc-url=jdbc:derby:oaktest\;create=true
{noformat}
> Build timed out
> ---
>
> Key: OAK-5534
> URL: https://issues.apache.org/jira/browse/OAK-5534
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
> Labels: test-failure
> Fix For: 1.0.38
>
> Attachments: console-1432-document-rdb.txt, console-1432-segment.txt,
> console.txt
>
>
> Jenkins CI failure:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7
> (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK
> 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting
> #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/]
> [console
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (OAK-5534) Build timed out
[ https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-5534: - Attachment: (was: console-1432.txt) > Build timed out > --- > > Key: OAK-5534 > URL: https://issues.apache.org/jira/browse/OAK-5534 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: test-failure > Fix For: 1.0.38 > > Attachments: console-1432-document-rdb.txt, console-1432-segment.txt, > console.txt > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting > #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5534) Build timed out
[ https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-5534: - Attachment: console-1432-segment.txt console-1432-document-rdb.txt > Build timed out > --- > > Key: OAK-5534 > URL: https://issues.apache.org/jira/browse/OAK-5534 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: test-failure > Fix For: 1.0.38 > > Attachments: console-1432-document-rdb.txt, console-1432-segment.txt, > console.txt > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting > #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OAK-5700) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 failed
[ https://issues.apache.org/jira/browse/OAK-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu resolved OAK-5700. -- Resolution: Duplicate > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 failed > --- > > Key: OAK-5700 > URL: https://issues.apache.org/jira/browse/OAK-5700 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting > #1432|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1432/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1432/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OAK-5700) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 failed
[ https://issues.apache.org/jira/browse/OAK-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu closed OAK-5700. > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 failed > --- > > Key: OAK-5700 > URL: https://issues.apache.org/jira/browse/OAK-5700 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting > #1432|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1432/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1432/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (OAK-5534) Build timed out
[
https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871404#comment-15871404
]
Alex Parvulescu edited comment on OAK-5534 at 2/17/17 8:23 AM:
---
attached log from failing build 1432
{noformat}
[integrationTesting] $ /home/jenkins/tools/maven/apache-maven-3.2.1/bin/mvn
"-Djdk=JDK 1.8 (latest)" -Dprofile=integrationTesting "-DUbuntu Slaves=ubuntu"
-Dnsfixtures=DOCUMENT_RDB clean verify -PintegrationTesting
-Dstandby.test.timeout=5000 -Dsurefire.skip.ut=true -Dmongo.port=9
-Prdb-derby -DREMOVEMErdb.jdbc-url=jdbc:derby:oaktest\;create=true
{noformat}
was (Author: alex.parvulescu):
log from failing build 1432
> Build timed out
> ---
>
> Key: OAK-5534
> URL: https://issues.apache.org/jira/browse/OAK-5534
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
> Labels: test-failure
> Fix For: 1.0.38
>
> Attachments: console-1432.txt, console.txt
>
>
> Jenkins CI failure:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7
> (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK
> 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting
> #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/]
> [console
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (OAK-5699) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 failed
[ https://issues.apache.org/jira/browse/OAK-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu closed OAK-5699. > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 failed > > > Key: OAK-5699 > URL: https://issues.apache.org/jira/browse/OAK-5699 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting > #1432|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1432/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1432/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OAK-5534) Build timed out
[ https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-5534: - Attachment: console-1432.txt log from failing build 1432 > Build timed out > --- > > Key: OAK-5534 > URL: https://issues.apache.org/jira/browse/OAK-5534 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: test-failure > Fix For: 1.0.38 > > Attachments: console-1432.txt, console.txt > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting > #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OAK-5699) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 failed
[ https://issues.apache.org/jira/browse/OAK-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu resolved OAK-5699. -- Resolution: Duplicate > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 failed > > > Key: OAK-5699 > URL: https://issues.apache.org/jira/browse/OAK-5699 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting > #1432|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1432/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1432/console] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
