[jira] [Commented] (OAK-5626) ChangeProcessor doesn't reset 'blocking' flag when items from queue gets removed and commit-rate-limiter is null

2017-02-16 Thread Vikas Saurabh (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871328#comment-15871328
 ] 

Vikas Saurabh commented on OAK-5626:


Thanks for pointing it out [~reschke]. Would take a look.

> ChangeProcessor doesn't reset 'blocking' flag when items from queue gets 
> removed and commit-rate-limiter is null
> 
>
> Key: OAK-5626
> URL: https://issues.apache.org/jira/browse/OAK-5626
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Minor
>  Labels: candidate_oak_1_0
> Fix For: 1.2.24, 1.4.14, 1.7.0, 1.8, 1.6.1
>
> Attachments: OAK-5626.patch, OAK-5626-v2.patch, OAK-5626-v3.patch
>
>
> Following up on conversation at \[0]:
> {{ChangeProcessor#queueSizeChanged}} \[1] sets blocking flag to true if queue 
> size is hit (or beyond). The warning "Revision queue is full. Further 
> revisions will be compacted." is logged only when it *wasn't* blocking.
> BUT, when queue empties, blocking flag is reset inside if block for 
> commitRateLimiter!=null. That means an event chain like: 
> # qFull
> # log warn
> # qEmpties
> # qFull 
> won't log the WARN after step(4)
> \[0]: http://markmail.org/message/hgein5g3ohyjhw5n
> \[1]: 
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/observation/ChangeProcessor.java#L307



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5626) ChangeProcessor doesn't reset 'blocking' flag when items from queue gets removed and commit-rate-limiter is null

2017-02-16 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871319#comment-15871319
 ] 

Julian Reschke commented on OAK-5626:
-

[~catholicon] - are you aware of the test failures, such as 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1429/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.jcr.observation/ObservationQueueFullWarnTest/warnOnRepeatedQueueFull_MemoryNodeStore_/

> ChangeProcessor doesn't reset 'blocking' flag when items from queue gets 
> removed and commit-rate-limiter is null
> 
>
> Key: OAK-5626
> URL: https://issues.apache.org/jira/browse/OAK-5626
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Minor
>  Labels: candidate_oak_1_0
> Fix For: 1.2.24, 1.4.14, 1.7.0, 1.8, 1.6.1
>
> Attachments: OAK-5626.patch, OAK-5626-v2.patch, OAK-5626-v3.patch
>
>
> Following up on conversation at \[0]:
> {{ChangeProcessor#queueSizeChanged}} \[1] sets blocking flag to true if queue 
> size is hit (or beyond). The warning "Revision queue is full. Further 
> revisions will be compacted." is logged only when it *wasn't* blocking.
> BUT, when queue empties, blocking flag is reset inside if block for 
> commitRateLimiter!=null. That means an event chain like: 
> # qFull
> # log warn
> # qEmpties
> # qFull 
> won't log the WARN after step(4)
> \[0]: http://markmail.org/message/hgein5g3ohyjhw5n
> \[1]: 
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/observation/ChangeProcessor.java#L307



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (OAK-5626) ChangeProcessor doesn't reset 'blocking' flag when items from queue gets removed and commit-rate-limiter is null

2017-02-16 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871319#comment-15871319
 ] 

Julian Reschke edited comment on OAK-5626 at 2/17/17 7:17 AM:
--

[~catholicon] - are you aware of the test failures, such as in

https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1429/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.jcr.observation/ObservationQueueFullWarnTest/warnOnRepeatedQueueFull_MemoryNodeStore_/

?


was (Author: reschke):
[~catholicon] - are you aware of the test failures, such as 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1429/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.jcr.observation/ObservationQueueFullWarnTest/warnOnRepeatedQueueFull_MemoryNodeStore_/

> ChangeProcessor doesn't reset 'blocking' flag when items from queue gets 
> removed and commit-rate-limiter is null
> 
>
> Key: OAK-5626
> URL: https://issues.apache.org/jira/browse/OAK-5626
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Minor
>  Labels: candidate_oak_1_0
> Fix For: 1.2.24, 1.4.14, 1.7.0, 1.8, 1.6.1
>
> Attachments: OAK-5626.patch, OAK-5626-v2.patch, OAK-5626-v3.patch
>
>
> Following up on conversation at \[0]:
> {{ChangeProcessor#queueSizeChanged}} \[1] sets blocking flag to true if queue 
> size is hit (or beyond). The warning "Revision queue is full. Further 
> revisions will be compacted." is logged only when it *wasn't* blocking.
> BUT, when queue empties, blocking flag is reset inside if block for 
> commitRateLimiter!=null. That means an event chain like: 
> # qFull
> # log warn
> # qEmpties
> # qFull 
> won't log the WARN after step(4)
> \[0]: http://markmail.org/message/hgein5g3ohyjhw5n
> \[1]: 
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/observation/ChangeProcessor.java#L307



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5699) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 failed

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871317#comment-15871317
 ] 

Hudson commented on OAK-5699:
-

Previously failing build now is OK.
 Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting 
#1433|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1433/]
 [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/1433/console]

> 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] [Commented] (OAK-4804) Synonym analyzer with multiple words in synonym definition can give more results than expected

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871309#comment-15871309
 ] 

Chetan Mehrotra commented on OAK-4804:
--

bq. The only way that I can think of fixing this is to allow for different 
analyzer for index and querying time.

Bit late here but yes I think we need to have such a support.

> Synonym analyzer with multiple words in synonym definition can give more 
> results than expected
> --
>
> Key: OAK-4804
> URL: https://issues.apache.org/jira/browse/OAK-4804
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Minor
>
> Setting up synonyms such as {{"FTW, For the win"}} would also return 
> documents which contain all of {{"For", "the", "win"}}.
> Test case:
> {noformat}
> @Test
> public void fulltextSearchWithPhraseSynonymAnalyzer() throws Exception {
> Tree idx = createFulltextIndex(root.getTree("/"), "test");
> TestUtil.useV2(idx);
> Tree anl = 
> idx.addChild(LuceneIndexConstants.ANALYZERS).addChild(LuceneIndexConstants.ANL_DEFAULT);
> 
> anl.addChild(LuceneIndexConstants.ANL_TOKENIZER).setProperty(LuceneIndexConstants.ANL_NAME,
>  "Standard");
> Tree synFilter = 
> anl.addChild(LuceneIndexConstants.ANL_FILTERS).addChild("Synonym");
> synFilter.setProperty("synonyms", "syn.txt");
> 
> synFilter.addChild("syn.txt").addChild(JCR_CONTENT).setProperty(JCR_DATA, 
> "FTW, For the win");
> Tree test = root.getTree("/").addChild("test");
> test.addChild("1").setProperty("foo", "FTW");
> test.addChild("2").setProperty("foo", "For the win");
> test.addChild("3").setProperty("foo", "For gods sake, this is not the 
> way to win it");
> root.commit();
> assertQuery("select * from [nt:base] where CONTAINS(*, 'FTW') AND 
> ISDESCENDANTNODE('/test')",
> asList("/test/1", "/test/2"));//current (failing result is 
> ["/test/1", "/test/2", "/test/3"])
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871304#comment-15871304
 ] 

Chetan Mehrotra commented on OAK-5692:
--

bq. 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.

>From code it looks like only '=>' format is supported. 

However looking at docs it appears that this filter should only be applied in 
either index or query time and not both [1] [2] [3]. So with current design in 
Oak this might not work reliably

[~catholicon] Thoughts?

[1] 
http://stackoverflow.com/questions/9998480/how-to-use-synonymfilterfactory-in-solr
[2] 
http://stackoverflow.com/questions/12217024/solr-synonyms-containing-multiple-words
[3] https://nolanlawson.com/2012/10/31/better-synonym-handling-in-solr/

> 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 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 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] [Commented] (OAK-5700) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 failed

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871303#comment-15871303
 ] 

Hudson commented on OAK-5700:
-

Previously failing build now is OK.
 Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
#1433|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1433/]
 [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/1433/console]

> 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] [Commented] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871294#comment-15871294
 ] 

Chetan Mehrotra commented on OAK-5692:
--

Updated docs in http://svn.apache.org/viewvc?rev=1783334=rev

[~empire29] Can you have a look. Would publish once all such details are 
explained there

> 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 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 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] [Assigned] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra reassigned OAK-5692:


Assignee: Chetan Mehrotra

> 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 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 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] [Commented] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871280#comment-15871280
 ] 

Chetan Mehrotra commented on OAK-5692:
--

{quote}
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?
{quote}

That appears to be Oak level limitation. Did not anticipated that. Can you open 
an Oak issue for that? Should be easy to support

> 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
>
> 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 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] [Commented] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871271#comment-15871271
 ] 

Chetan Mehrotra commented on OAK-5692:
--

bq. 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?)

See javadocs for below and look for subclasses
* 
https://lucene.apache.org/core/4_7_1/analyzers-common/org/apache/lucene/analysis/util/TokenFilterFactory.html
* CharFilters - 
https://lucene.apache.org/core/4_7_1/analyzers-common/org/apache/lucene/analysis/util/CharFilterFactory.html
* Filters - 
https://lucene.apache.org/core/4_7_1/analyzers-common/org/apache/lucene/analysis/util/TokenFilterFactory.html

Per PorterStemFilterFactory it does not appear to support ignorecase [1]

bq. 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.

Support for factories was moved from Solr to Lucene. So roughly its 1:1 mapping 
here
[1] 
https://lucene.apache.org/core/4_7_1/analyzers-common/org/apache/lucene/analysis/en/PorterStemFilterFactory.html

> 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
>
> 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 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] [Comment Edited] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871246#comment-15871246
 ] 

Chetan Mehrotra edited comment on OAK-5692 at 2/17/17 6:23 AM:
---

bq. 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?

Currently only one analyzer canbe configured. That can be done by either
# Specifying a default analyzer directly via its classname
# OR via composing Tokenizers, TokenFilters and CharFilters

bq. By default is the analyzer index AND query time, unless specified by 
`type=index|query` property?

Currently same analyzer is used for both query and index.

Reason for having a config name of "anakyzers" was to allow support for 
configuring more analyzers and having them used in different context for 
different properties. So far no one asked for that hence this part is not 
extended!

bq. What is the naming for multiple analyzer nodes?

Not possible as mentioned in previous section

bq. The Stop filters words property must be a String not String[] and the value 
is a comma delimited String value. 

Yes. All config values must be string. No other JCR type should be used here


was (Author: chetanm):
bq. 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?

Currently only one analyzer canbe configured. That can be done by either
# Specifying a default analyzer directly via its classname
# OR via composing Tokenizers, TokenFilters and CharFilters

bq. By default is the analyzer index AND query time, unless specified by 
`type=index|query` property?

Currently same analyzer is used for both query and index.

Reason for having a config name of "anakyzers" was to allow support for 
configuring more analyzers and having them used in different context for 
different properties. So far no one asked for that hence this part is not 
extended!

bq. The Stop filters words property must be a String not String[] and the value 
is a comma delimited String value. 

Yes. All config values must be string. No other JCR type should be used here

> 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
>
> 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 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

[jira] [Created] (OAK-5699) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1432 failed

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5699:
---

 Summary: 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] [Created] (OAK-5700) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1432 failed

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5700:
---

 Summary: 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] [Commented] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871246#comment-15871246
 ] 

Chetan Mehrotra commented on OAK-5692:
--

bq. 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?

Currently only one analyzer canbe configured. That can be done by either
# Specifying a default analyzer directly via its classname
# OR via composing Tokenizers, TokenFilters and CharFilters

bq. By default is the analyzer index AND query time, unless specified by 
`type=index|query` property?

Currently same analyzer is used for both query and index.

Reason for having a config name of "anakyzers" was to allow support for 
configuring more analyzers and having them used in different context for 
different properties. So far no one asked for that hence this part is not 
extended!

bq. The Stop filters words property must be a String not String[] and the value 
is a comma delimited String value. 

Yes. All config values must be string. No other JCR type should be used here

> 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
>
> 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 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

2017-02-16 Thread Chetan Mehrotra (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra 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 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 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 based Stop

[jira] [Commented] (OAK-5608) Test failure: org.apache.jackrabbit.mk.util.CommitGateIT.test

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871123#comment-15871123
 ] 

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 
#459|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/459/]
 [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/459/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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871113#comment-15871113
 ] 

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 
#459|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/459/]
 [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/459/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] [Updated] (OAK-5624) Test failure: org.apache.jackrabbit.oak.cache.ConcurrentTest.testLoaderBlock

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain updated OAK-5624:
---
Fix Version/s: (was: 1.8)
   1.0.38

> Test failure: org.apache.jackrabbit.oak.cache.ConcurrentTest.testLoaderBlock
> 
>
> Key: OAK-5624
> URL: https://issues.apache.org/jira/browse/OAK-5624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, core
>Affects Versions: 1.0.36
>Reporter: Hudson
>  Labels: test-failure, windows
> Fix For: 1.0.38
>
> 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_NS,profile=unittesting #445 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #445|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=unittesting/445/]
>  [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=unittesting/445/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5609) Test failure: org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest.concurrentObservers

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain updated OAK-5609:
---
Fix Version/s: 1.0.38

> Test failure: 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserverTest.concurrentObservers
> -
>
> Key: OAK-5609
> URL: https://issues.apache.org/jira/browse/OAK-5609
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, core
>Affects Versions: 1.0.36
>Reporter: Hudson
>  Labels: test-failure, windows
> Fix For: 1.0.38
>
> 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.8 (unlimited security) 
> 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #443 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 
> #443|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/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=DOCUMENT_NS,profile=unittesting/443/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5697) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #458 failed

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-5697.

Resolution: Duplicate

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #458 failed
> 
>
> Key: OAK-5697
> URL: https://issues.apache.org/jira/browse/OAK-5697
> 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_NS,profile=unittesting #458 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #458|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=unittesting/458/]
>  [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=unittesting/458/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5698) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #458 failed

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-5698.

Resolution: Duplicate

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit 
> Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #458 failed
> 
>
> Key: OAK-5698
> URL: https://issues.apache.org/jira/browse/OAK-5698
> 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=SEGMENT_TAR,profile=unittesting #458 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited 
> security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,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=SEGMENT_TAR,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=SEGMENT_TAR,profile=unittesting/458/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (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

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-5696.

Resolution: Duplicate

> 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] [Resolved] (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

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-5694.

Resolution: Duplicate

> 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-5695) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871108#comment-15871108
 ] 

Hudson commented on OAK-5695:
-

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_NS,profile=integrationTesting 
#459|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/459/]
 [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/459/console]

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed
> ---
>
> Key: OAK-5695
> URL: https://issues.apache.org/jira/browse/OAK-5695
> 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_NS,profile=integrationTesting #457 
> 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 
> #457|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/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=DOCUMENT_NS,profile=integrationTesting/457/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (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

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-5693.

Resolution: Duplicate

> 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] [Resolved] (OAK-5695) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed

2017-02-16 Thread Amit Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-5695.

Resolution: Duplicate

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed
> ---
>
> Key: OAK-5695
> URL: https://issues.apache.org/jira/browse/OAK-5695
> 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_NS,profile=integrationTesting #457 
> 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 
> #457|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/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=DOCUMENT_NS,profile=integrationTesting/457/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5698) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #458 failed

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871097#comment-15871097
 ] 

Hudson commented on OAK-5698:
-

Build is still failing.
Failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 
64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting 
#459|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=unittesting/459/]
 [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=unittesting/459/console]

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit 
> Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #458 failed
> 
>
> Key: OAK-5698
> URL: https://issues.apache.org/jira/browse/OAK-5698
> 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=SEGMENT_TAR,profile=unittesting #458 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited 
> security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,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=SEGMENT_TAR,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=SEGMENT_TAR,profile=unittesting/458/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5697) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #458 failed

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871088#comment-15871088
 ] 

Hudson commented on OAK-5697:
-

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_NS,profile=unittesting 
#459|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=unittesting/459/]
 [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=unittesting/459/console]

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #458 failed
> 
>
> Key: OAK-5697
> URL: https://issues.apache.org/jira/browse/OAK-5697
> 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_NS,profile=unittesting #458 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #458|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=unittesting/458/]
>  [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=unittesting/458/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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871086#comment-15871086
 ] 

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 
#459|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/459/]
 [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/459/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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871076#comment-15871076
 ] 

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 
#459|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/459/]
 [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/459/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] [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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871072#comment-15871072
 ] 

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 
#459|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/459/]
 [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/459/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] [Commented] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871064#comment-15871064
 ] 

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 
#459|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/459/]
 [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/459/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] [Commented] (OAK-5608) Test failure: org.apache.jackrabbit.mk.util.CommitGateIT.test

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870980#comment-15870980
 ] 

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 
#458|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/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=SEGMENT_TAR,profile=integrationTesting/458/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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870949#comment-15870949
 ] 

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 
#458|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/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_NS,profile=unittesting/458/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-5695) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870947#comment-15870947
 ] 

Hudson commented on OAK-5695:
-

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_NS,profile=integrationTesting 
#458|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/458/]
 [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/458/console]

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed
> ---
>
> Key: OAK-5695
> URL: https://issues.apache.org/jira/browse/OAK-5695
> 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_NS,profile=integrationTesting #457 
> 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 
> #457|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/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=DOCUMENT_NS,profile=integrationTesting/457/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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870921#comment-15870921
 ] 

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 
#458|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/458/]
 [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/458/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] [Created] (OAK-5698) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=unittesting #458 failed

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5698:
---

 Summary: Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 
(unlimited security) 64-bit Windows 
only,nsfixtures=SEGMENT_TAR,profile=unittesting #458 failed
 Key: OAK-5698
 URL: https://issues.apache.org/jira/browse/OAK-5698
 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=SEGMENT_TAR,profile=unittesting #458 has failed.
First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited 
security) 64-bit Windows only,nsfixtures=SEGMENT_TAR,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=SEGMENT_TAR,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=SEGMENT_TAR,profile=unittesting/458/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OAK-5697) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #458 failed

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5697:
---

 Summary: Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 
(unlimited security) 64-bit Windows 
only,nsfixtures=DOCUMENT_NS,profile=unittesting #458 failed
 Key: OAK-5697
 URL: https://issues.apache.org/jira/browse/OAK-5697
 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_NS,profile=unittesting #458 has failed.
First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited 
security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
#458|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=unittesting/458/]
 [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=unittesting/458/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870862#comment-15870862
 ] 

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 
#458|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/458/]
 [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/458/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] [Created] (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

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5696:
---

 Summary: 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] [Commented] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870827#comment-15870827
 ] 

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 
#458|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/458/]
 [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/458/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] [Commented] (OAK-5608) Test failure: org.apache.jackrabbit.mk.util.CommitGateIT.test

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870770#comment-15870770
 ] 

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 
#457|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/457/]
 [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/457/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

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870758#comment-15870758
 ] 

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 
#457|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/457/]
 [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/457/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] [Created] (OAK-5695) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5695:
---

 Summary: Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 
(unlimited security) 64-bit Windows 
only,nsfixtures=DOCUMENT_NS,profile=integrationTesting #457 failed
 Key: OAK-5695
 URL: https://issues.apache.org/jira/browse/OAK-5695
 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_NS,profile=integrationTesting #457 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 
#457|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/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=DOCUMENT_NS,profile=integrationTesting/457/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (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

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5694:
---

 Summary: 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] [Created] (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

2017-02-16 Thread Hudson (JIRA) 
Hudson created OAK-5693:
---

 Summary: 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] [Commented] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870683#comment-15870683
 ] 

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 
#457|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/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=DOCUMENT_RDB,profile=unittesting/457/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] [Updated] (OAK-5654) Improve log output with UserImporter

2017-02-16 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-5654:

Fix Version/s: 1.6.1

> Improve log output with UserImporter
> 
>
> Key: OAK-5654
> URL: https://issues.apache.org/jira/browse/OAK-5654
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core
>Reporter: angela
>Assignee: angela
>Priority: Trivial
> Fix For: 1.7.0, 1.6.1
>
>
> The {{UserImporter}} logs a misleading warning when unable to handle a 
> property unrelated to user/group import. Since the {{ProtectedItemImporter}} 
> implementation are just asked to handle a given protected item, it's 
> confusing to mark this a WARNing, it should just be for information purpose 
> on DEBUG level.
> While reviewing this I also got the impression that the importer is too 
> verbose wrt besteffort handling of group membership. Would suggest to set 
> this from INFO to DEBUG too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (OAK-5654) Improve log output with UserImporter

2017-02-16 Thread angela (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865939#comment-15865939
 ] 

angela edited comment on OAK-5654 at 2/16/17 6:09 PM:
--

trunk: Committed revision 1782973.
1.6 branch: Committed revision 1783263.




was (Author: anchela):
Committed revision 1782973.


> Improve log output with UserImporter
> 
>
> Key: OAK-5654
> URL: https://issues.apache.org/jira/browse/OAK-5654
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core
>Reporter: angela
>Assignee: angela
>Priority: Trivial
> Fix For: 1.7.0, 1.6.1
>
>
> The {{UserImporter}} logs a misleading warning when unable to handle a 
> property unrelated to user/group import. Since the {{ProtectedItemImporter}} 
> implementation are just asked to handle a given protected item, it's 
> confusing to mark this a WARNing, it should just be for information purpose 
> on DEBUG level.
> While reviewing this I also got the impression that the importer is too 
> verbose wrt besteffort handling of group membership. Would suggest to set 
> this from INFO to DEBUG too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5678) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5678.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
> (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1427 failed
> ---
>
> Key: OAK-5678
> URL: https://issues.apache.org/jira/browse/OAK-5678
> 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 #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1427/]
>  [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/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5679) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5679.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1427 failed
> ---
>
> Key: OAK-5679
> URL: https://issues.apache.org/jira/browse/OAK-5679
> 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_NS,profile=integrationTesting #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1427/]
>  [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/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5668:
-
Fix Version/s: 1.2.24

> 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] [Closed] (OAK-5682) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #456 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5682.


> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #456 failed
> 
>
> Key: OAK-5682
> URL: https://issues.apache.org/jira/browse/OAK-5682
> 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_NS,profile=unittesting #456 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #456|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=unittesting/456/]
>  [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=unittesting/456/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5682) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #456 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5682.
--
Resolution: Duplicate

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting #456 failed
> 
>
> Key: OAK-5682
> URL: https://issues.apache.org/jira/browse/OAK-5682
> 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_NS,profile=unittesting #456 has 
> failed.
> First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.7 (unlimited 
> security) 64-bit Windows only,nsfixtures=DOCUMENT_NS,profile=unittesting 
> #456|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=unittesting/456/]
>  [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=unittesting/456/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (OAK-5679) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5679.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1427 failed
> ---
>
> Key: OAK-5679
> URL: https://issues.apache.org/jira/browse/OAK-5679
> 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_NS,profile=integrationTesting #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1427/]
>  [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/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5668:
-
Affects Version/s: 1.2.23

> 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.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] [Closed] (OAK-5678) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5678.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
> (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1427 failed
> ---
>
> Key: OAK-5678
> URL: https://issues.apache.org/jira/browse/OAK-5678
> 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 #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1427/]
>  [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/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread David Gonzalez (JIRA) 

 [ 
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 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 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{noforma} 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 based Stop

[jira] [Updated] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread David Gonzalez (JIRA) 

 [ 
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 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 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.

[1]  http://jackrabbit.apache.org/oak/docs/query/lucene.html
[2] 
https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#Specifying_an_Analyzer_in_the_schema

  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?
* 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.

[1]  http://jackrabbit.apache.org/oak/docs/query/lucene.html
[2] 
https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#Specifying_an_Analyzer_in_the_schema


> Oak Lucene analyzers docs unclear on viable configurations
> --
>
> Key: OAK-5692
>

[jira] [Updated] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread David Gonzalez (JIRA) 

 [ 
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 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 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.

[1]  http://jackrabbit.apache.org/oak/docs/query/lucene.html
[2] 
https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#Specifying_an_Analyzer_in_the_schema

  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 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]

[jira] [Closed] (OAK-5675) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #455 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5675.


> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #455 failed
> -
>
> Key: OAK-5675
> URL: https://issues.apache.org/jira/browse/OAK-5675
> 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 #455 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 
> #455|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/455/]
>  [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/455/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OAK-5692) Oak Lucene analyzers docs unclear on viable configurations

2017-02-16 Thread David Gonzalez (JIRA) 
David Gonzalez created OAK-5692:
---

 Summary: 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


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?
* 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.

[1]  http://jackrabbit.apache.org/oak/docs/query/lucene.html
[2] 
https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#Specifying_an_Analyzer_in_the_schema



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5675) Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #455 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5675.
--
Resolution: Duplicate

> Build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) 64-bit 
> Windows only,nsfixtures=DOCUMENT_RDB,profile=unittesting #455 failed
> -
>
> Key: OAK-5675
> URL: https://issues.apache.org/jira/browse/OAK-5675
> 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 #455 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 
> #455|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/455/]
>  [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/455/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5470) Test failure: SecurityProviderRegistrationTest.testSecurityConfigurations2

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5470:
-
Labels: test-failure windows  (was: test-failure)

> Test failure: SecurityProviderRegistrationTest.testSecurityConfigurations2
> --
>
> Key: OAK-5470
> URL: https://issues.apache.org/jira/browse/OAK-5470
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, pojosr
>Affects Versions: 1.4.13
>Reporter: Hudson
>  Labels: test-failure, windows
> Fix For: 1.4.14
>
> Attachments: sysout-1380.log, unit-tests-build-1371.log, 
> unit-tests.log
>
>
> 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 #1371 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting 
> #1371|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1371/]
>  [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/1371/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5470) Test failure: SecurityProviderRegistrationTest.testSecurityConfigurations2

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5470:
-
Affects Version/s: 1.4.13

> Test failure: SecurityProviderRegistrationTest.testSecurityConfigurations2
> --
>
> Key: OAK-5470
> URL: https://issues.apache.org/jira/browse/OAK-5470
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, pojosr
>Affects Versions: 1.4.13
>Reporter: Hudson
>  Labels: test-failure, windows
> Fix For: 1.4.14
>
> Attachments: sysout-1380.log, unit-tests-build-1371.log, 
> unit-tests.log
>
>
> 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 #1371 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting 
> #1371|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1371/]
>  [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/1371/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5579) Test failure: ExternalPrivateStoreIT

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5579:
-
Fix Version/s: 1.0.38

> Test failure: ExternalPrivateStoreIT
> 
>
> Key: OAK-5579
> URL: https://issues.apache.org/jira/browse/OAK-5579
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, segmentmk
>Affects Versions: 1.0.36
>Reporter: Hudson
>  Labels: test-failure
> Fix For: 1.0.38
>
> Attachments: unit-tests.log
>
>
> 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 #1402 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting 
> #1402|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1402/]
>  [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/1402/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5676) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5676.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
> (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed
> --
>
> Key: OAK-5676
> URL: https://issues.apache.org/jira/browse/OAK-5676
> 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_MK,profile=integrationTesting #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (OAK-5676) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5676.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 
> (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed
> --
>
> Key: OAK-5676
> URL: https://issues.apache.org/jira/browse/OAK-5676
> 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_MK,profile=integrationTesting #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (OAK-5677) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5677.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed
> --
>
> Key: OAK-5677
> URL: https://issues.apache.org/jira/browse/OAK-5677
> 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=integrationTesting #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5677) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5677.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1427 failed
> --
>
> Key: OAK-5677
> URL: https://issues.apache.org/jira/browse/OAK-5677
> 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=integrationTesting #1427 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting 
> #1427|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1427/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5680) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1428 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5680.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1428 failed
> ---
>
> Key: OAK-5680
> URL: https://issues.apache.org/jira/browse/OAK-5680
> 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 #1428 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting 
> #1428|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=unittesting/1428/]
>  [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/1428/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (OAK-5680) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1428 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5680.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_MK,profile=unittesting #1428 failed
> ---
>
> Key: OAK-5680
> URL: https://issues.apache.org/jira/browse/OAK-5680
> 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 #1428 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_MK,profile=unittesting 
> #1428|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=unittesting/1428/]
>  [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/1428/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (OAK-5683) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1429 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5683.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1429 failed
> -
>
> Key: OAK-5683
> URL: https://issues.apache.org/jira/browse/OAK-5683
> 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 #1429 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting 
> #1429|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1429/]
>  [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/1429/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5668:
-
Affects Version/s: 1.4.13

> 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.4.13
>Reporter: Hudson
>  Labels: test-failure, ubuntu, windows
> Fix For: 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] [Updated] (OAK-5668) Test failure: observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu updated OAK-5668:
-
Fix Version/s: 1.4.15

> 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.4.13
>Reporter: Hudson
>  Labels: test-failure, ubuntu, windows
> Fix For: 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] [Resolved] (OAK-5683) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1429 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5683.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1429 failed
> -
>
> Key: OAK-5683
> URL: https://issues.apache.org/jira/browse/OAK-5683
> 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 #1429 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting 
> #1429|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1429/]
>  [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/1429/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (OAK-5681) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1428 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu closed OAK-5681.


> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1428 failed
> 
>
> Key: OAK-5681
> URL: https://issues.apache.org/jira/browse/OAK-5681
> 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 #1428 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting 
> #1428|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1428/]
>  [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/1428/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OAK-5681) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1428 failed

2017-02-16 Thread Alex Parvulescu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Parvulescu resolved OAK-5681.
--
Resolution: Duplicate

> Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 
> (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1428 failed
> 
>
> Key: OAK-5681
> URL: https://issues.apache.org/jira/browse/OAK-5681
> 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 #1428 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting 
> #1428|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1428/]
>  [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/1428/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-3134) Identify functionality offered by oak-run

2017-02-16 Thread Thomas Mueller (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870128#comment-15870128
 ] 

Thomas Mueller commented on OAK-3134:
-

I think we need to discuss again about the goal of this issue.

* Why split? Is it size, if yes why is 50 MB a problem?
* If it's about size, could we simply remove large libraries such as Hadoop 
(see comments above)?
* If it's not about size, what is it then? (tested vs untested tools? target 
audience?)

Moving source code from oak-run closer to the implementation seems orthogonal 
to me.

> 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] [Updated] (OAK-3070) Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs

2017-02-16 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-3070:

Attachment: OAK-3070-updated.patch

patch update to apply to trunk (also logging slightly extended)

> Use a lower bound in VersionGC query to avoid checking unmodified once 
> deleted docs
> ---
>
> Key: OAK-3070
> URL: https://issues.apache.org/jira/browse/OAK-3070
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: mongomk, rdbmk
>Reporter: Chetan Mehrotra
>Assignee: Vikas Saurabh
>  Labels: performance
> Attachments: OAK-3070.patch, OAK-3070-updated.patch, 
> OAK-3070-updated.patch
>
>
> As part of OAK-3062 [~mreutegg] suggested
> {quote}
> As a further optimization we could also limit the lower bound of the _modified
> range. The revision GC does not need to check documents with a _deletedOnce
> again if they were not modified after the last successful GC run. If they
> didn't change and were considered existing during the last run, then they
> must still exist in the current GC run. To make this work, we'd need to
> track the last successful revision GC run. 
> {quote}
> Lowest last validated _modified can be possibly saved in settings collection 
> and reused for next run



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (OAK-3070) Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs

2017-02-16 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-3070:

Comment: was deleted

(was: patch update to apply to trunk)

> Use a lower bound in VersionGC query to avoid checking unmodified once 
> deleted docs
> ---
>
> Key: OAK-3070
> URL: https://issues.apache.org/jira/browse/OAK-3070
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: mongomk, rdbmk
>Reporter: Chetan Mehrotra
>Assignee: Vikas Saurabh
>  Labels: performance
> Attachments: OAK-3070.patch, OAK-3070-updated.patch
>
>
> As part of OAK-3062 [~mreutegg] suggested
> {quote}
> As a further optimization we could also limit the lower bound of the _modified
> range. The revision GC does not need to check documents with a _deletedOnce
> again if they were not modified after the last successful GC run. If they
> didn't change and were considered existing during the last run, then they
> must still exist in the current GC run. To make this work, we'd need to
> track the last successful revision GC run. 
> {quote}
> Lowest last validated _modified can be possibly saved in settings collection 
> and reused for next run



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-3134) Identify functionality offered by oak-run

2017-02-16 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870081#comment-15870081
 ] 

Michael Dürig commented on OAK-3134:


I think there is two different aspects here:

1. Feature bloat and maintainability of {{oak-run}}: moving the various tools 
closer to the implementations makes them simpler to implement, maintain and 
test. {{oak-run}} would simply become an unified entry point and an assembly 
for distribution. See [~frm]'s post on oak-dev \[1] and OAK-5437. 

2. Separating different types of functionality. Independently of how we call it 
we should ask ourselves for each particular piece of tooling: Is is safe to 
use? Is it stable enough? Do we tests it? Is it well documented? Is it useful 
for a user of Oak or a product build on top of it? Only if we can answer these 
questions with yes should the tool be publicly recommended. In other cases the 
tool should either not be distributed in the same assembly or come with a 
disclaimer of some sort. The former approach is AFAIU what [~edivad] intents 
with the separation into distinct modules "operation" and "development". The 
latter is more like what Git is doing with its separation into "Porcelain" and 
"Plumbing". 

\[1] http://markmail.org/message/6ypw57uqowzrxfli

> 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] [Updated] (OAK-3070) Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs

2017-02-16 Thread Julian Reschke (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-3070:

Attachment: OAK-3070-updated.patch

patch update to apply to trunk

> Use a lower bound in VersionGC query to avoid checking unmodified once 
> deleted docs
> ---
>
> Key: OAK-3070
> URL: https://issues.apache.org/jira/browse/OAK-3070
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: mongomk, rdbmk
>Reporter: Chetan Mehrotra
>Assignee: Vikas Saurabh
>  Labels: performance
> Attachments: OAK-3070.patch, OAK-3070-updated.patch
>
>
> As part of OAK-3062 [~mreutegg] suggested
> {quote}
> As a further optimization we could also limit the lower bound of the _modified
> range. The revision GC does not need to check documents with a _deletedOnce
> again if they were not modified after the last successful GC run. If they
> didn't change and were considered existing during the last run, then they
> must still exist in the current GC run. To make this work, we'd need to
> track the last successful revision GC run. 
> {quote}
> Lowest last validated _modified can be possibly saved in settings collection 
> and reused for next run



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-3134) Identify functionality offered by oak-run

2017-02-16 Thread Alex Parvulescu (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870012#comment-15870012
 ] 

Alex Parvulescu commented on OAK-3134:
--

bq. The terms "operations" and "development" sound quite fuzzy (to me).
I agree with the sentiment. It seems we're putting a lot of resources into 
splitting the 2, and I'm not convinced about the end goal here. I definitely 
want to have the _development_ deployed to maven central, if we end up 
splitting. how else would I get feedback on it? how could one feature 
transition from _development_ into _operations_ if it's not available for use?

If we need to split, I would bundle both into the same jar and simply output a 
warning when using _development_ stuff along the lines of 'you are using dev 
stuff, stuff might break, take special care'.

bq. I would prefer moving "benchmarks" (not listed above) to a new module
+1. if we simply move benchmarks to a jar that is not deployed, does that not 
suffice for our bandwidth saving goals?



> 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] [Updated] (OAK-5534) Build timed out

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominique Jäggi updated OAK-5534:
-
Fix Version/s: (was: 1.0.37)
   1.0.38

> 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.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-5542) Test failure: security.authentication.ldap.LdapProviderTest (Address already in use)

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominique Jäggi updated OAK-5542:
-
Fix Version/s: (was: 1.0.37)
   1.0.38

> Test failure: security.authentication.ldap.LdapProviderTest (Address already 
> in use)
> 
>
> Key: OAK-5542
> URL: https://issues.apache.org/jira/browse/OAK-5542
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: auth-ldap, continuous integration
>Reporter: Hudson
>  Labels: test-failure
> Fix For: 1.4.14, 1.0.38
>
>
> 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=integrationTesting #1390 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
> #1390|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1390/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1390/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5264) Test failure: SolrIndexHookIT.testPropertyAddition

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominique Jäggi updated OAK-5264:
-
Fix Version/s: (was: 1.0.37)
   1.0.38

> Test failure: SolrIndexHookIT.testPropertyAddition
> --
>
> Key: OAK-5264
> URL: https://issues.apache.org/jira/browse/OAK-5264
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Affects Versions: 1.0.35, 1.2.22, 1.5.15
>Reporter: Hudson
>Assignee: Tommaso Teofili
>  Labels: test-failure
> Fix For: 1.2.24, 1.0.38
>
>
> 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=integrationTesting #1323 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
> #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/]
>  [console 
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5404) Test failure: SolrIndexQueryTestIT.testNativeMLTQuery and testNativeMLTQueryWithStream

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominique Jäggi updated OAK-5404:
-
Fix Version/s: (was: 1.0.37)
   1.0.38

> Test failure:  SolrIndexQueryTestIT.testNativeMLTQuery and 
> testNativeMLTQueryWithStream
> ---
>
> Key: OAK-5404
> URL: https://issues.apache.org/jira/browse/OAK-5404
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Affects Versions: 1.0
>Reporter: Thomas Mueller
>Assignee: Tommaso Teofili
>  Labels: test-failure
> Fix For: 1.0.38
>
>
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.jackrabbit.oak.plugins.index.solr.query.SolrIndexQueryTestIT.testNativeMLTQueryWithStream(SolrIndexQueryTestIT.java:286)
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.jackrabbit.oak.plugins.index.solr.query.SolrIndexQueryTestIT.testNativeMLTQuery(SolrIndexQueryTestIT.java:264)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5530) Test failure: security.authentication.ldap.LdapLoginStandaloneTest

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominique Jäggi updated OAK-5530:
-
Fix Version/s: (was: 1.0.37)
   1.0.38

> Test failure: security.authentication.ldap.LdapLoginStandaloneTest
> --
>
> Key: OAK-5530
> URL: https://issues.apache.org/jira/browse/OAK-5530
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: auth-ldap, continuous integration
>Reporter: Hudson
>  Labels: test-failure
> Fix For: 1.0.38
>
>
> 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 #1384 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting 
> #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1384/]
>  [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/1384/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5532) Test failure: segment.standby.ExternalSharedStoreIT/BrokenNetworkTest.test...

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominique Jäggi updated OAK-5532:
-
Fix Version/s: (was: 1.0.37)
   1.0.38

> Test failure: segment.standby.ExternalSharedStoreIT/BrokenNetworkTest.test...
> -
>
> Key: OAK-5532
> URL: https://issues.apache.org/jira/browse/OAK-5532
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, segmentmk
>Reporter: Hudson
>  Labels: test-failure
> Fix For: 1.2.24, 1.0.38
>
> Attachments: build1401-unit-tests.log, unit-tests.log
>
>
> 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 #1384 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 
> 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting 
> #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1384/]
>  [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/1384/console]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-3134) Identify functionality offered by oak-run

2017-02-16 Thread Davide Giannella (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869971#comment-15869971
 ] 

Davide Giannella commented on OAK-3134:
---

[~tmueller]
bq.  "threaddump": I use that mainly to analyze production problems, but 
sometimes also during development. So it's not strictly development nor 
operations. "persistentcache" is similar.

I think that the difference between operations and development can be explained 
as well in this way: are any potential consumers/customers using those directly 
on a production instance? Are those used to maintain any oak deplyment? Or are 
they mainly used by us, developer, to diagnose, or measure?

the main difference will be that the _development_ will *not* be deployed to 
maven and therefore in order to use it, someone will have to be able to 
checkout sources and compile. 

bq. The terms "operations" and "development" sound quite fuzzy (to me).

we can reconsider the naming. I don't mind.

> 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] [Updated] (OAK-3598) Export cache related classes for usage in other oak bundle

2017-02-16 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-3598:

Labels: tech-debt  (was: )

> Export cache related classes for usage in other oak bundle
> --
>
> Key: OAK-3598
> URL: https://issues.apache.org/jira/browse/OAK-3598
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: cache
>Reporter: Chetan Mehrotra
>  Labels: tech-debt
> Fix For: 1.8
>
>
> For OAK-3092 oak-lucene would need to access classes from 
> {{org.apache.jackrabbit.oak.cache}} package. For now its limited to 
> {{CacheStats}} to expose the cache related statistics.
> This task is meant to determine steps needed to export the package 
> * Update the pom.xml to export the package
> * Review current set of classes to see if they need to be reviewed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (OAK-3598) Export cache related classes for usage in other oak bundle

2017-02-16 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela reopened OAK-3598:
-
  Assignee: (was: Chetan Mehrotra)

IMHO we should take another look at this for 1.8

> Export cache related classes for usage in other oak bundle
> --
>
> Key: OAK-3598
> URL: https://issues.apache.org/jira/browse/OAK-3598
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: cache
>Reporter: Chetan Mehrotra
>  Labels: tech-debt
> Fix For: 1.8
>
>
> For OAK-3092 oak-lucene would need to access classes from 
> {{org.apache.jackrabbit.oak.cache}} package. For now its limited to 
> {{CacheStats}} to expose the cache related statistics.
> This task is meant to determine steps needed to export the package 
> * Update the pom.xml to export the package
> * Review current set of classes to see if they need to be reviewed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-3598) Export cache related classes for usage in other oak bundle

2017-02-16 Thread angela (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angela updated OAK-3598:

Fix Version/s: 1.8

> Export cache related classes for usage in other oak bundle
> --
>
> Key: OAK-3598
> URL: https://issues.apache.org/jira/browse/OAK-3598
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: cache
>Reporter: Chetan Mehrotra
>  Labels: tech-debt
> Fix For: 1.8
>
>
> For OAK-3092 oak-lucene would need to access classes from 
> {{org.apache.jackrabbit.oak.cache}} package. For now its limited to 
> {{CacheStats}} to expose the cache related statistics.
> This task is meant to determine steps needed to export the package 
> * Update the pom.xml to export the package
> * Review current set of classes to see if they need to be reviewed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5666) oak-upgrade should validate the paths

2017-02-16 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/OAK-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869701#comment-15869701
 ] 

Tomek Rękawek commented on OAK-5666:


Backported to 1.6 in [r1783193|https://svn.apache.org/r1783193].

> oak-upgrade should validate the paths
> -
>
> Key: OAK-5666
> URL: https://issues.apache.org/jira/browse/OAK-5666
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: upgrade
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Fix For: 1.7.0, 1.8, 1.6.1
>
>
> Passing an invalid path (eg. one with the trailing slash) causes some hard to 
> detect issues with the migrated repository. Paths passed to 
> \{include,exclude,merge\}-paths options should be validated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5651) java.lang.IllegalStateException logged when migrating Segment to Document

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek updated OAK-5651:
---
Fix Version/s: 1.6.1

> java.lang.IllegalStateException logged when migrating Segment to Document
> -
>
> Key: OAK-5651
> URL: https://issues.apache.org/jira/browse/OAK-5651
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Affects Versions: 1.5.13
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Fix For: 1.7.0, 1.8, 1.6.1
>
> Attachments: OAK-5651.patch
>
>
> After migrating the SegmentMK to DocumentMK following exception is logged:
> {noformat}
> 12:38:58.816 INFO  [main] RepositorySidegrade.java:310  Copying 
> checkpoints is not supported for this combination of node stores
> 12:38:58.835 ERROR [main] BackgroundObserver.java:176   Uncaught 
> exception in 
> org.apache.jackrabbit.oak.plugins.document.bundlor.BundlingConfigHandler@3c782d8e
> com.google.common.util.concurrent.UncheckedExecutionException: 
> java.lang.IllegalStateException: Missing external change for branch revision:
> at 
> com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2199) 
> ~[guava-15.0.jar:na]
> at com.google.common.cache.LocalCache.get(LocalCache.java:3932) 
> ~[guava-15.0.jar:na]
> at 
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4721) 
> ~[guava-15.0.jar:na]
> at 
> org.apache.jackrabbit.oak.plugins.document.MemoryDiffCache.getChanges(MemoryDiffCache.java:83)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.TieredDiffCache.getChanges(TieredDiffCache.java:50)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.compare(DocumentNodeStore.java:1616)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.AbstractDocumentNodeState.compareAgainstBaseState(AbstractDocumentNodeState.java:114)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.process(EditorDiff.java:52) 
> ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.bundlor.BundlingConfigHandler.contentChanged(BundlingConfigHandler.java:70)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:134)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_73]
> at 
> com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:297)
>  [guava-15.0.jar:na]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1.run(BackgroundObserver.java:148)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.commons.concurrent.NotifyingFutureTask.run(NotifyingFutureTask.java:73)
>  [oak-commons-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.commons.concurrent.NotifyingFutureTask.onComplete(NotifyingFutureTask.java:62)
>  [oak-commons-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver.contentChanged(BackgroundObserver.java:312)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:52)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:80)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore$4.headOfQueue(DocumentNodeStore.java:837)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.CommitQueue.waitUntilHeadOfQueue(CommitQueue.java:237)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.CommitQueue.done(CommitQueue.java:92)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.done(DocumentNodeStore.java:816)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1585)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
>

[jira] [Resolved] (OAK-5691) Remove duplicated code from FileStore and ReadOnlyFileStore

2017-02-16 Thread Francesco Mari (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OAK-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Mari resolved OAK-5691.
-
   Resolution: Fixed
Fix Version/s: 1.7.0

Fixed at r1783195.

> Remove duplicated code from FileStore and ReadOnlyFileStore
> ---
>
> Key: OAK-5691
> URL: https://issues.apache.org/jira/browse/OAK-5691
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.7.0, 1.8
>
>
> {{FileStore}} and {{ReadOnlyFileStore}} duplicate the code used to check if a 
> segment is contained in one of the {{TarReader}} and the code to read a 
> segment entry from the list of {{TarReader}} instances. This code should be 
> extracted and reused from both {{FileStore}} and {{ReadOnlyFileStore}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OAK-5666) oak-upgrade should validate the paths

2017-02-16 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/OAK-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomek Rękawek updated OAK-5666:
---
Fix Version/s: 1.6.1

> oak-upgrade should validate the paths
> -
>
> Key: OAK-5666
> URL: https://issues.apache.org/jira/browse/OAK-5666
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: upgrade
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Fix For: 1.7.0, 1.8, 1.6.1
>
>
> Passing an invalid path (eg. one with the trailing slash) causes some hard to 
> detect issues with the migrated repository. Paths passed to 
> \{include,exclude,merge\}-paths options should be validated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OAK-5651) java.lang.IllegalStateException logged when migrating Segment to Document

2017-02-16 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/OAK-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869699#comment-15869699
 ] 

Tomek Rękawek commented on OAK-5651:


Backported to 1.6 in [r1783192|https://svn.apache.org/r1783192].

> java.lang.IllegalStateException logged when migrating Segment to Document
> -
>
> Key: OAK-5651
> URL: https://issues.apache.org/jira/browse/OAK-5651
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Affects Versions: 1.5.13
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Fix For: 1.7.0, 1.8, 1.6.1
>
> Attachments: OAK-5651.patch
>
>
> After migrating the SegmentMK to DocumentMK following exception is logged:
> {noformat}
> 12:38:58.816 INFO  [main] RepositorySidegrade.java:310  Copying 
> checkpoints is not supported for this combination of node stores
> 12:38:58.835 ERROR [main] BackgroundObserver.java:176   Uncaught 
> exception in 
> org.apache.jackrabbit.oak.plugins.document.bundlor.BundlingConfigHandler@3c782d8e
> com.google.common.util.concurrent.UncheckedExecutionException: 
> java.lang.IllegalStateException: Missing external change for branch revision:
> at 
> com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2199) 
> ~[guava-15.0.jar:na]
> at com.google.common.cache.LocalCache.get(LocalCache.java:3932) 
> ~[guava-15.0.jar:na]
> at 
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4721) 
> ~[guava-15.0.jar:na]
> at 
> org.apache.jackrabbit.oak.plugins.document.MemoryDiffCache.getChanges(MemoryDiffCache.java:83)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.TieredDiffCache.getChanges(TieredDiffCache.java:50)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.compare(DocumentNodeStore.java:1616)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.AbstractDocumentNodeState.compareAgainstBaseState(AbstractDocumentNodeState.java:114)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.process(EditorDiff.java:52) 
> ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.bundlor.BundlingConfigHandler.contentChanged(BundlingConfigHandler.java:70)
>  ~[oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:134)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_73]
> at 
> com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:297)
>  [guava-15.0.jar:na]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1.run(BackgroundObserver.java:148)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.commons.concurrent.NotifyingFutureTask.run(NotifyingFutureTask.java:73)
>  [oak-commons-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.commons.concurrent.NotifyingFutureTask.onComplete(NotifyingFutureTask.java:62)
>  [oak-commons-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver.contentChanged(BackgroundObserver.java:312)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:52)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:80)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore$4.headOfQueue(DocumentNodeStore.java:837)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.CommitQueue.waitUntilHeadOfQueue(CommitQueue.java:237)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.CommitQueue.done(CommitQueue.java:92)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.done(DocumentNodeStore.java:816)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1585)
>  [oak-core-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at 
>

  1   2   >