[jira] [Commented] (SOLR-4969) Enable ChaosMonkeyNothingIsSafeTest

[ https://issues.apache.org/jira/browse/SOLR-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695297#comment-13695297 ] Uwe Schindler commented on SOLR-4969: - Unstable as before. Can you revert and disable a

[jira] [Reopened] (SOLR-4969) Enable ChaosMonkeyNothingIsSafeTest

[ https://issues.apache.org/jira/browse/SOLR-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reopened SOLR-4969: - > Enable ChaosMonkeyNothingIsSafeTest > --- > > Ke

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #893: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/893/ 2 tests failed. FAILED: org.apache.solr.cloud.BasicDistributedZkTest.org.apache.solr.cloud.BasicDistributedZkTest Error Message: 1 thread leaked from SUITE scope at org.apache.solr.cloud.BasicDistributedZkTest: 1) Thread[id=

[jira] [Commented] (SOLR-4969) Enable ChaosMonkeyNothingIsSafeTest

[ https://issues.apache.org/jira/browse/SOLR-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695374#comment-13695374 ] Mark Miller commented on SOLR-4969: --- No, its not like before... And no, I'm not ready to

[jira] [Commented] (SOLR-4967) Frequent test fails in org.apache.solr.cloud.SyncSliceTest

[ https://issues.apache.org/jira/browse/SOLR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695393#comment-13695393 ] Mark Miller commented on SOLR-4967: --- Okay, I've got some decent logging in place - anothe

Re: Test failure locally, something about solrconfig.snippet.randomindexconfig

OK, found it. Two problems: 1> OpenCloseCoreStressTest constructs various sub-directories for cores, bypassing the place where the included XML snippet is copied to the same dir as solrconfig-minimal.xml. Easy fix. 2> The test swallows the exception rather than failing, I can fix that too. Sorry

[jira] [Commented] (SOLR-4960) race condition in CoreContainer.shutdown leads to double closes on cores

[ https://issues.apache.org/jira/browse/SOLR-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695494#comment-13695494 ] Erick Erickson commented on SOLR-4960: -- [~yo...@apache.org] What's the state of all th

[jira] [Created] (SOLR-4974) Consolidate and simplify closing cores in container shutdown.

Erick Erickson created SOLR-4974: Summary: Consolidate and simplify closing cores in container shutdown. Key: SOLR-4974 URL: https://issues.apache.org/jira/browse/SOLR-4974 Project: Solr Iss

[jira] [Created] (SOLR-4975) SOLR CONSOLE DISPLAYING STATUS NOT CURRENT AFTER DELTA IMPORT

mohammad created SOLR-4975: -- Summary: SOLR CONSOLE DISPLAYING STATUS NOT CURRENT AFTER DELTA IMPORT Key: SOLR-4975 URL: https://issues.apache.org/jira/browse/SOLR-4975 Project: Solr Issue Type: Bug

[jira] [Closed] (SOLR-4975) SOLR CONSOLE DISPLAYING STATUS NOT CURRENT AFTER DELTA IMPORT

[ https://issues.apache.org/jira/browse/SOLR-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson closed SOLR-4975. Resolution: Invalid Please raise this question on the Solr user's list rather than raise a JIRA unt

Re: The commit-tag-bot...

Well JIRA locked out the new user pretty right away…sweet… Also cannot log him in even if I solve the required captcha - that or I just can't solve captchas for the life of me. Will see if I can reset it by email or not. - Mark On Jun 27, 2013, at 8:45 PM, Steve Rowe wrote: > Hey Mark, > >

[jira] [Resolved] (SOLR-4967) Frequent test fails in org.apache.solr.cloud.SyncSliceTest

[ https://issues.apache.org/jira/browse/SOLR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-4967. --- Resolution: Fixed This should be fixed now. It was a test issue - the distrib update processor would

Re: The commit-tag-bot...

Ah well, no go. If I try and send a pw reset link, it says its sent it and I never get it. If I try and send the username to the registered email address I used, it says that address does not exist. If I try and login as the user and solve the captcha, it doesn't work. If I make a new user, I'm

[jira] [Commented] (SOLR-4975) SOLR CONSOLE DISPLAYING STATUS NOT CURRENT AFTER DELTA IMPORT

[ https://issues.apache.org/jira/browse/SOLR-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695525#comment-13695525 ] mohammad commented on SOLR-4975: Thanks for you quick response ... will do that.

[jira] [Created] (LUCENE-5081) Compress doc ID sets

Adrien Grand created LUCENE-5081: Summary: Compress doc ID sets Key: LUCENE-5081 URL: https://issues.apache.org/jira/browse/LUCENE-5081 Project: Lucene - Core Issue Type: Improvement

[jira] [Updated] (LUCENE-5014) ANTLR Lucene query parser

[ https://issues.apache.org/jira/browse/LUCENE-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Chyla updated LUCENE-5014: Attachment: LUCENE-5014.txt The patch that *actually* contains the extended parser with NEAR opera

Re: The commit-tag-bot...

Thanks for the effort Mark, sorry it was such a pain. I've filed a JIRA to switch to using svngit2jira for LUCENE and SOLR issues (following ): . Steve On Jun 28, 2013, at 11:45 AM, Mark Miller wrote: >

[jira] [Updated] (SOLR-4968) The collection alias api should have a list cmd.

[ https://issues.apache.org/jira/browse/SOLR-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-4968: -- Attachment: SOLR-4968.patch First patch. Response needs some tweaking, test needs some asserts.

[jira] [Updated] (LUCENE-5081) Compress doc ID sets

[ https://issues.apache.org/jira/browse/LUCENE-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5081: - Attachment: LUCENE-5081.patch Here is an implementation of a compressed doc ID set. Although it

[jira] [Commented] (SOLR-4945) Japanese Autocomplete and Highlighter broken

[ https://issues.apache.org/jira/browse/SOLR-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695587#comment-13695587 ] Shruthi Khatawkar commented on SOLR-4945: - Thanks All. Regards, Shruthi

[jira] [Created] (SOLR-4976) info stream doesn't work with merged segment warmer

Ryan Ernst created SOLR-4976: Summary: info stream doesn't work with merged segment warmer Key: SOLR-4976 URL: https://issues.apache.org/jira/browse/SOLR-4976 Project: Solr Issue Type: Bug

[jira] [Resolved] (SOLR-4539) Consistently failing seed for SyncSliceTest

[ https://issues.apache.org/jira/browse/SOLR-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-4539. --- Resolution: Fixed Fix Version/s: 5.0 > Consistently failing seed for SyncSliceTest > --

[jira] [Commented] (SOLR-4565) Extend NorwegianMinimalStemFilter to handle "nynorsk"

[ https://issues.apache.org/jira/browse/SOLR-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695709#comment-13695709 ] Jan Høydahl commented on SOLR-4565: --- Thanks Robert! > Extend NorwegianMi

[jira] [Commented] (SOLR-4976) info stream doesn't work with merged segment warmer

[ https://issues.apache.org/jira/browse/SOLR-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695710#comment-13695710 ] Robert Muir commented on SOLR-4976: --- +1... i TODO's this instead of cleaning up properly

[jira] [Commented] (SOLR-4221) Custom sharding

[ https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695723#comment-13695723 ] Jan Høydahl commented on SOLR-4221: --- bq. If you wish to create a new collection/shard w/o

[JENKINS] Lucene-trunk-Linux-Java7-64-test-only - Build # 51118 - Failure!

Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/51118/ 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.lucene.search.TestMultiTermConstantScore Error Message: count should be <= maxMergeCount (= 1) Stack Trace: java.lang.IllegalArgumentException: count should

Re: [JENKINS] Lucene-trunk-Linux-Java7-64-test-only - Build # 51118 - Failure!

ill look into this... its https://issues.apache.org/jira/browse/LUCENE-5080:) On Fri, Jun 28, 2013 at 4:01 PM, wrote: > Build: > builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/51118/ > > 3 tests failed. > FAILED: > junit.framework.TestSuite.org.apache.lucene.search.TestMultiTerm

Re: [JENKINS] Lucene-trunk-Linux-Java7-64-test-only - Build # 51118 - Failure!

I committed a fix On Fri, Jun 28, 2013 at 4:08 PM, Robert Muir wrote: > ill look into this... its > https://issues.apache.org/jira/browse/LUCENE-5080 :) > > On Fri, Jun 28, 2013 at 4:01 PM, wrote: > >> Build: >> builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/51118/ >> >> 3 tests

[jira] [Commented] (SOLR-4221) Custom sharding

[ https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695754#comment-13695754 ] Yonik Seeley commented on SOLR-4221: bq. Do we really need to have so many configuratio

[jira] [Updated] (SOLR-4976) info stream doesn't work with merged segment warmer

[ https://issues.apache.org/jira/browse/SOLR-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4976: - Attachment: SOLR-4976.patch First try at a patch, with a simple test. > info stream doesn

[jira] [Commented] (SOLR-4976) info stream doesn't work with merged segment warmer

[ https://issues.apache.org/jira/browse/SOLR-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695777#comment-13695777 ] Mark Miller commented on SOLR-4976: --- Nice, +1. > info stream doesn't wor

[jira] [Commented] (SOLR-4787) Join Contrib

[ https://issues.apache.org/jira/browse/SOLR-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695802#comment-13695802 ] Kranti Parisa commented on SOLR-4787: - Joel, Yes, sort implementation would be costly,

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0-ea-b94) - Build # 6357 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/6357/ Java: 64bit/jdk1.8.0-ea-b94 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. REGRESSION: org.apache.lucene.index.TestIndexWriterReader.testAddIndexesAndDoDeletesThreads Error Message: count should be >= maxThreadC

Re: [JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0-ea-b94) - Build # 6357 - Failure!

im just gonna go fix https://issues.apache.org/jira/browse/LUCENE-5080 On Fri, Jun 28, 2013 at 4:41 PM, Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/6357/ > Java: 64bit/jdk1.8.0-ea-b94 -XX:+UseCompressedOops -XX:+UseConcMar

[JENKINS] Lucene-trunk-Linux-Java7-64-test-only - Build # 51144 - Failure!

Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/51144/ 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.lucene.search.TestFieldCacheRangeFilter Error Message: count should be >= maxThreadCount (= 4) Stack Trace: java.lang.IllegalArgumentException: count should

[jira] [Created] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

Ryan Ernst created SOLR-4977: Summary: info stream in solrconfig should have option for writing to the solr log Key: SOLR-4977 URL: https://issues.apache.org/jira/browse/SOLR-4977 Project: Solr

[jira] [Commented] (LUCENE-5080) CMS setters cannot work unless you setMaxMergeCount before you setMaxThreadCount

[ https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695939#comment-13695939 ] Robert Muir commented on LUCENE-5080: - {quote} Maybe instead we can have CMS.reset(in

[jira] [Created] (LUCENE-5082) For SolrQueryParserBase.getPrefixQuery(String field, String termStr), use BytesRef from calling FieldType.readableToIndexed for Term

Jessica Cheng created LUCENE-5082: - Summary: For SolrQueryParserBase.getPrefixQuery(String field, String termStr), use BytesRef from calling FieldType.readableToIndexed for Term Key: LUCENE-5082 URL: https://issue

[jira] [Updated] (LUCENE-5082) For SolrQueryParserBase.getPrefixQuery(String field, String termStr), use BytesRef from calling FieldType.readableToIndexed for Term

[ https://issues.apache.org/jira/browse/LUCENE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Cheng updated LUCENE-5082: -- Description: Currently, SolrQueryParserBase.getFieldQuery calls FieldType.getFieldQuery, which

[jira] [Commented] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695956#comment-13695956 ] Mark Miller commented on SOLR-4977: --- +1, this would be nice. > info stre

[jira] [Updated] (LUCENE-5080) CMS setters cannot work unless you setMaxMergeCount before you setMaxThreadCount

[ https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-5080: Attachment: LUCENE-5080.patch here's my patch. To address Shai's concern, i just combined the two

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #894: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/894/ 2 tests failed. FAILED: org.apache.solr.cloud.BasicDistributedZkTest.org.apache.solr.cloud.BasicDistributedZkTest Error Message: 1 thread leaked from SUITE scope at org.apache.solr.cloud.BasicDistributedZkTest: 1) Thread[id=

[jira] [Updated] (SOLR-4976) info stream doesn't work with merged segment warmer

[ https://issues.apache.org/jira/browse/SOLR-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4976: - Attachment: SOLR-4976.patch New patch removing null check on close() since IndexWriterConfig does not allo

[jira] [Updated] (LUCENE-5080) CMS setters cannot work unless you setMaxMergeCount before you setMaxThreadCount

[ https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-5080: Attachment: LUCENE-5080.patch updated patch: some solr tests depended on these previous setters wi

[jira] [Resolved] (LUCENE-5080) CMS setters cannot work unless you setMaxMergeCount before you setMaxThreadCount

[ https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-5080. - Resolution: Fixed Fix Version/s: 4.4 5.0 I committed the new setter. I

[JENKINS] Lucene-Solr-4.x-Linux (32bit/ibm-j9-jdk6) - Build # 6285 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/6285/ Java: 32bit/ibm-j9-jdk6 -Xjit:exclude={org/apache/lucene/util/fst/FST.pack(IIF)Lorg/apache/lucene/util/fst/FST;} 1 tests failed. REGRESSION: org.apache.lucene.index.TestNRTThreads.testNRTThreads Error Message: count should be >=

[jira] [Commented] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696007#comment-13696007 ] Ryan Ernst commented on SOLR-4977: -- This patch adds a LoggingInfoStream in solr which just

[jira] [Updated] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4977: - Attachment: SOLR-4977.patch > info stream in solrconfig should have option for writing to the solr log

[jira] [Created] (SOLR-4978) Time is stripped from datetime column when imported into Solr date field

Bill Au created SOLR-4978: - Summary: Time is stripped from datetime column when imported into Solr date field Key: SOLR-4978 URL: https://issues.apache.org/jira/browse/SOLR-4978 Project: Solr Issue

[jira] [Commented] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696014#comment-13696014 ] Robert Muir commented on SOLR-4977: --- Looks pretty good: two comments: * This might be use

[jira] [Updated] (SOLR-4894) Add a new update processor factory that will dynamically add fields to the schema if an input document contains unknown fields

[ https://issues.apache.org/jira/browse/SOLR-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-4894: - Attachment: SOLR-4894.patch Patch, I think it's ready to go. > Add a new update processor

[jira] [Resolved] (SOLR-4976) info stream doesn't work with merged segment warmer

[ https://issues.apache.org/jira/browse/SOLR-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved SOLR-4976. --- Resolution: Fixed Fix Version/s: 4.4 5.0 Thanks Ryan! > inf

[jira] [Updated] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4977: - Attachment: SOLR-4977.patch New patch addressing Robert's comments. > info stream in solr

[jira] [Commented] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696029#comment-13696029 ] Robert Muir commented on SOLR-4977: --- my only other comment is i think it should go to slf

[jira] [Commented] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696030#comment-13696030 ] Robert Muir commented on SOLR-4977: --- And we probably want to fix the verbage/examples und

[jira] [Updated] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4977: - Attachment: SOLR-4977.patch {quote} my only other comment is i think it should go to slf4j with LoggerFac

change verbose [junit4:junit4] to just [junit4] and save horizontal space?

i feel like this is a no-brainer, but there might be some regexps for jenkins that could break or something else i'm not aware of: Index: lucene/common-build.xml === --- lucene/common-build.xml(revision 1497957) +++ lucene/common-

[jira] [Updated] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4977: - Attachment: SOLR-4977.patch Attempting to upload the patch again to get the newer version...

[jira] [Updated] (SOLR-4977) info stream in solrconfig should have option for writing to the solr log

[ https://issues.apache.org/jira/browse/SOLR-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst updated SOLR-4977: - Attachment: SOLR-4977.patch SOLR-4977.patch And one more with the hdfs example config file

Re: change verbose [junit4:junit4] to just [junit4] and save horizontal space?

+1 - I think the Jenkins regexps can handle either (and can certainly be changed if not) On Jun 28, 2013, at 11:55 PM, Robert Muir wrote: > i feel like this is a no-brainer, but there might be some regexps for jenkins > that could break or something else i'm not aware of: > > Index: lucene/co

RE: change verbose [junit4:junit4] to just [junit4] and save horizontal space?

Let's do that. I love the taskname="..." attribute! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Steve Rowe [mailto:sar...@gmail.com] > Sent: Saturday, June 29, 2013 6:36 AM > To: dev@lucene.apache.or