RE: [VOTE] Lucene/Solr 4.8.0 RC2

Here is my +1: SUCCESS! [1:53:39.982427] Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Uwe Schindler [mailto:u...@thetaphi.de] > Sent: Thursday, April 24, 2014 11:54 PM > To: dev@lucene.apache.org

maxThreads in Jetty

In the /etc/jetty.xml delivered with Solr, maxThreads is set to 10,000. I wonder why maxThreads for Jetty with Solr is so high? The default case for a Solr instance is that processing is isolated to machines controlled by the owner: Performance is dictated by local CPU, memory & storage latency.

[jira] [Commented] (SOLR-6006) Separate test and compile scope dependencies in the Solrj ivy.xml file, so that the derived Maven dependencies get filled out properly in the Solrj POM

[ https://issues.apache.org/jira/browse/SOLR-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980734#comment-13980734 ] ASF subversion and git services commented on SOLR-6006: --- Commit 15899

[jira] [Commented] (SOLR-6006) Separate test and compile scope dependencies in the Solrj ivy.xml file, so that the derived Maven dependencies get filled out properly in the Solrj POM

[ https://issues.apache.org/jira/browse/SOLR-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980731#comment-13980731 ] ASF subversion and git services commented on SOLR-6006: --- Commit 15899

[jira] [Updated] (SOLR-6006) Separate test and compile scope dependencies in the Solrj ivy.xml file, so that the derived Maven dependencies get filled out properly in the Solrj POM

[ https://issues.apache.org/jira/browse/SOLR-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-6006: - Summary: Separate test and compile scope dependencies in the Solrj ivy.xml file, so that the derived Maven

[jira] [Updated] (SOLR-6006) Separate test and compile scope dependencies in the Solrj ivy.xml file, so that maven dependencies' scope can be specified appropriately, and the derived Maven dependencie

[ https://issues.apache.org/jira/browse/SOLR-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-6006: - Summary: Separate test and compile scope dependencies in the Solrj ivy.xml file, so that maven dependencie

Re: [VOTE] Lucene/Solr 4.8.0 RC2

: => http://people.apache.org/~uschindler/staging_area/lucene-solr-4.8.0-RC2-rev1589874/ +1 to artifacts with these sha1.. 970ac0e7461362213a191b451a1569b1e41f87a1 *lucene-4.8.0-src.tgz 8c70e4cafbf313ae23f958a09d4fa45f72598b4b *lucene-4.8.0.tgz 1d653b2ce78e0986846d100e0bac43665e09c902 *lucene

[jira] [Comment Edited] (SOLR-2894) Implement distributed pivot faceting

[ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980662#comment-13980662 ] Trey Grainger edited comment on SOLR-2894 at 4/25/14 3:54 AM: --

[jira] [Commented] (SOLR-2894) Implement distributed pivot faceting

[ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980662#comment-13980662 ] Trey Grainger commented on SOLR-2894: - Hi [~otis], I appreciate your interest here. Tha

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980661#comment-13980661 ] Erick Erickson commented on SOLR-6003: -- bq: ...is that atomic updates do not work *ev

Re: [VOTE] Lucene/Solr 4.8.0 RC2

+1 SUCCESS! [1:05:39.093694] On Fri, Apr 25, 2014 at 3:24 AM, Uwe Schindler wrote: > Hi, > > I prepared a second release candidate of Lucene and Solr 4.8.0. The > artifacts can be found here: > => > http://people.apache.org/~uschindler/staging_area/lucene-solr-4.8.0-RC2-rev1589874/ > > This RC

Re: [VOTE] Lucene/Solr 4.8.0 RC2

SUCCESS! [0:40:44.239391] +1 --  Mark Miller about.me/markrmiller On April 24, 2014 at 5:54:38 PM, Uwe Schindler (u...@thetaphi.de) wrote: Hi, I prepared a second release candidate of Lucene and Solr 4.8.0. The artifacts can be found here: => http://people.apache.org/~uschindler/staging_

[jira] [Commented] (LUCENE-5559) Argument validation for TokenFilters having numeric constructor parameter(s)

[ https://issues.apache.org/jira/browse/LUCENE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980625#comment-13980625 ] ASF subversion and git services commented on LUCENE-5559: - Commit

[jira] [Commented] (SOLR-2894) Implement distributed pivot faceting

[ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980624#comment-13980624 ] Otis Gospodnetic commented on SOLR-2894: If nobody volunteers, since this doesn't c

[jira] [Commented] (LUCENE-5559) Argument validation for TokenFilters having numeric constructor parameter(s)

[ https://issues.apache.org/jira/browse/LUCENE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980617#comment-13980617 ] ASF subversion and git services commented on LUCENE-5559: - Commit

Re: VOTE: RC0 Release apache-solr-ref-guide-4.8.pdf

Probably worthy of respin: 1. Yonik mentioned that the “configSet” param is misspelled as “configset" (on RC0 PDF p304): 2. In sect

[jira] [Commented] (SOLR-2894) Implement distributed pivot faceting

[ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980597#comment-13980597 ] Trey Grainger commented on SOLR-2894: - >>[~markrmil...@gmail.com] said: >>We should get

[jira] [Comment Edited] (SOLR-4478) Allow cores to specify a named config set in non-SolrCloud mode

[ https://issues.apache.org/jira/browse/SOLR-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980548#comment-13980548 ] Yonik Seeley edited comment on SOLR-4478 at 4/25/14 1:17 AM: - D

[jira] [Comment Edited] (SOLR-4478) Allow cores to specify a named config set in non-SolrCloud mode

[ https://issues.apache.org/jira/browse/SOLR-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980548#comment-13980548 ] Yonik Seeley edited comment on SOLR-4478 at 4/25/14 1:08 AM: - D

Re: [VOTE] Lucene/Solr 4.8.0 RC2

+1 SUCCESS! [0:41:40.344336] On Thu, Apr 24, 2014 at 5:54 PM, Uwe Schindler wrote: > Hi, > > I prepared a second release candidate of Lucene and Solr 4.8.0. The artifacts > can be found here: > => > http://people.apache.org/~uschindler/staging_area/lucene-solr-4.8.0-RC2-rev1589874/ > > This RC

[jira] [Commented] (SOLR-4478) Allow cores to specify a named config set in non-SolrCloud mode

[ https://issues.apache.org/jira/browse/SOLR-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980548#comment-13980548 ] Yonik Seeley commented on SOLR-4478: Does anyone have a simple working example they cou

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980539#comment-13980539 ] Kingston Duffie commented on SOLR-6003: --- Based on remarks from Hoss Man and Erick, I'

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980531#comment-13980531 ] Hoss Man commented on SOLR-6003: if i'm correctly following the gist of what you guys are a

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980522#comment-13980522 ] Kingston Duffie commented on SOLR-6003: --- Shawn, Unless I'm mistaken, the field that

Re: [VOTE] Lucene/Solr 4.8.0 RC2

+1 SUCCESS! [0:54:53.451061] Steve On Apr 24, 2014, at 5:54 PM, Uwe Schindler wrote: > Hi, > > I prepared a second release candidate of Lucene and Solr 4.8.0. The artifacts > can be found here: > => > http://people.apache.org/~uschindler/staging_area/lucene-solr-4.8.0-RC2-rev1589874/ > >

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980513#comment-13980513 ] Shawn Heisey commented on SOLR-6003: I have not looked at the code that generates the s

[jira] [Commented] (SOLR-5981) Please change method visibility of getSolrWriter in DataImportHandler to public (or at least protected)

[ https://issues.apache.org/jira/browse/SOLR-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980508#comment-13980508 ] Aaron LaBella commented on SOLR-5981: - Shawn, No problem, makes sense ... when you get

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980506#comment-13980506 ] Erick Erickson commented on SOLR-6003: -- Kingston: Yeah, there's an awful lot of "trib

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980496#comment-13980496 ] Kingston Duffie commented on SOLR-6003: --- I agree. Our ultimate goal, of course, is j

Re: VOTE: RC0 Release apache-solr-ref-guide-4.8.pdf

: Please VOTE to release the following RC0 as apache-solr-ref-guide-4.8.pdf ... : : https://dist.apache.org/repos/dist/dev/lucene/solr/ref-guide/apache-solr-ref-guide-4.8-RC0 +1 from me for this sha... a51de6f8b96fc302c57af4a174b19c1b1efc4fd9 apache-solr-ref-guide-4.8.pdf -Hoss http://www.l

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980465#comment-13980465 ] Erick Erickson commented on SOLR-6003: -- Hmmm, why not just an additional flag on the f

VOTE: RC0 Release apache-solr-ref-guide-4.8.pdf

(Note: cross posted to general, please confine replies to dev@) Please VOTE to release the following RC0 as apache-solr-ref-guide-4.8.pdf ... https://dist.apache.org/repos/dist/dev/lucene/solr/ref-guide/apache-solr-ref-guide-4.8-RC0 2 important notes about this RC... 1) Due to a known bug in

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1143/ 2 tests failed. REGRESSION: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testDistribSearch Error Message: Test abandoned because suite timeout was reached. Stack Trace: java.lang.Exception: Test abandoned because suite

[jira] [Commented] (LUCENE-5620) LowerCaseFilter.preserveOriginal

[ https://issues.apache.org/jira/browse/LUCENE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980426#comment-13980426 ] Ahmet Arslan commented on LUCENE-5620: -- [~rcmuir] , here is another ammo: ASCIIFold

[jira] [Commented] (SOLR-6003) JSON Update increment field with non-stored fields causes subtle problems

[ https://issues.apache.org/jira/browse/SOLR-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980415#comment-13980415 ] Shawn Heisey commented on SOLR-6003: "I thought of it later" followup: Instead of a fla

[VOTE] Lucene/Solr 4.8.0 RC2

Hi, I prepared a second release candidate of Lucene and Solr 4.8.0. The artifacts can be found here: => http://people.apache.org/~uschindler/staging_area/lucene-solr-4.8.0-RC2-rev1589874/ This RC contains the additional fixes for SOLR-6011, LUCENE-5626, and LUCENE-5630. Please check the art

[jira] [Commented] (SOLR-5981) Please change method visibility of getSolrWriter in DataImportHandler to public (or at least protected)

[ https://issues.apache.org/jira/browse/SOLR-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980307#comment-13980307 ] Shawn Heisey commented on SOLR-5981: I created a patch, but it hasn't been committed.

[jira] [Updated] (LUCENE-5569) Rename AtomicReader to LeafReader

[ https://issues.apache.org/jira/browse/LUCENE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrien Grand updated LUCENE-5569: - Priority: Blocker (was: Minor) > Rename AtomicReader to LeafReader > --

[jira] [Resolved] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler resolved LUCENE-5630. --- Resolution: Fixed Thanks Robert for reporting! > Improve TestAllAnalyzersHaveFactories > --

[jira] [Commented] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980232#comment-13980232 ] ASF subversion and git services commented on LUCENE-5630: - Commit

[jira] [Commented] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980229#comment-13980229 ] ASF subversion and git services commented on LUCENE-5630: - Commit

[jira] [Commented] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980225#comment-13980225 ] ASF subversion and git services commented on LUCENE-5630: - Commit

[JENKINS] Lucene-Solr-4.8-Linux (64bit/jdk1.8.0_05) - Build # 58 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.8-Linux/58/ Java: 64bit/jdk1.8.0_05 -XX:-UseCompressedOops -XX:+UseParallelGC 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.handler.admin.CoreAdminRequestStatusTest Error Message: 1 thread leaked from SUITE scope at org.ap

[jira] [Assigned] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reassigned LUCENE-5630: - Assignee: Uwe Schindler > Improve TestAllAnalyzersHaveFactories > --

[jira] [Updated] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-5630: -- Component/s: modules/analysis > Improve TestAllAnalyzersHaveFactories > --

[jira] [Commented] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980219#comment-13980219 ] Robert Muir commented on LUCENE-5630: - Looks great, thanks! > Improve TestAllAnalyze

[jira] [Updated] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-5630: -- Fix Version/s: 5.0 4.9 4.8 > Improve TestAllAnalyzersHav

[jira] [Updated] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

[ https://issues.apache.org/jira/browse/LUCENE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-5630: -- Attachment: LUCENE-5630.patch This patch fixes the issue. In fact the whole check was wrong a

[jira] [Commented] (LUCENE-5559) Argument validation for TokenFilters having numeric constructor parameter(s)

[ https://issues.apache.org/jira/browse/LUCENE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980202#comment-13980202 ] Ahmet Arslan commented on LUCENE-5559: -- bq. looks like i missed this patch? No, act

[jira] [Commented] (LUCENE-5559) Argument validation for TokenFilters having numeric constructor parameter(s)

[ https://issues.apache.org/jira/browse/LUCENE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980187#comment-13980187 ] Robert Muir commented on LUCENE-5559: - Oops, looks like i missed this patch? thanks A

[jira] [Commented] (LUCENE-5559) Argument validation for TokenFilters having numeric constructor parameter(s)

[ https://issues.apache.org/jira/browse/LUCENE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980175#comment-13980175 ] Ahmet Arslan commented on LUCENE-5559: -- Pinging [~rcmuir], if there is an interest f

[jira] [Updated] (SOLR-6013) Fix method visibility of Evaluator, refactor DateFormatEvaluator for extensibility

[ https://issues.apache.org/jira/browse/SOLR-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron LaBella updated SOLR-6013: Attachment: 0001-add-getters-for-datemathparser.patch one more small patch after fully testing the c

[jira] [Created] (LUCENE-5630) Improve TestAllAnalyzersHaveFactories

Robert Muir created LUCENE-5630: --- Summary: Improve TestAllAnalyzersHaveFactories Key: LUCENE-5630 URL: https://issues.apache.org/jira/browse/LUCENE-5630 Project: Lucene - Core Issue Type: Bug

Re: svn commit: r1589838 - in /lucene/dev/branches/branch_4x: ./ lucene/ lucene/analysis/ lucene/analysis/common/src/resources/META-INF/services/ lucene/analysis/common/src/test/org/apache/lucene/anal

Can you commit this to 4.8, because otherwise the uppercase factory does not work in solr. Its still time to do this. Uwe On 24. April 2014 21:18:40 MESZ, rm...@apache.org wrote: >Author: rmuir >Date: Thu Apr 24 19:18:39 2014 >New Revision: 1589838 > >URL: http://svn.apache.org/r1589838 >Log: >f

RE: [VOTE] Lucene/Solr 4.8.0 RC1

OK, I'll wait a bit and respin before going to bed (to give Jenkins a chance to test it finally) :-) Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: ysee...@gmail.com [mailto:ysee...@gmail.com] On

RE: svn commit: r1589782 - /lucene/dev/branches/branch_4x/lucene/core/src/test/org/apache/lucene/inde x/TestTerms.java

Another possibility that works is to move this test to a separate class, annotated with SuppressCodecs (if it does not depend on indexes created in beforeclass). Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980090#comment-13980090 ] Uwe Schindler commented on SOLR-6011: - OK, I removed the changes entry in trunk, too.

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980087#comment-13980087 ] ASF subversion and git services commented on SOLR-6011: --- Commit 15898

Re: svn commit: r1589782 - /lucene/dev/branches/branch_4x/lucene/core/src/test/org/apache/lucene/inde x/TestTerms.java

On Thu, Apr 24, 2014 at 12:31 PM, Michael McCandless wrote: > Yeah, I didn't want to disable the full test, just that one method, > because I want Terms.getMin/Max testing for Lucene3x too. > > Would be nice if we could @SuppressCodecs for just one method ... Thats impossible: many tests create t

[jira] [Resolved] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-6011. Resolution: Fixed > inOrder does not work with the complexphrase parser > --

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980071#comment-13980071 ] Yonik Seeley commented on SOLR-6011: That's OK... I realized that it was a new bug for

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980067#comment-13980067 ] Uwe Schindler commented on SOLR-6011: - Somehow because of merge conflict the changes go

Re: [VOTE] Lucene/Solr 4.8.0 RC1

On Thu, Apr 24, 2014 at 2:03 PM, Yonik Seeley wrote: > On Thu, Apr 24, 2014 at 1:57 PM, Uwe Schindler wrote: >> OK, >> I'll wait for the fix. Is this a new bug in 4.8? > > OK, thanks. It's an old bug in Lucene, but a new bug in Solr (since > complex phrase queries weren't exposed before). > I'll

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980060#comment-13980060 ] ASF subversion and git services commented on SOLR-6011: --- Commit 15898

[jira] [Commented] (SOLR-5981) Please change method visibility of getSolrWriter in DataImportHandler to public (or at least protected)

[ https://issues.apache.org/jira/browse/SOLR-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980061#comment-13980061 ] Aaron LaBella commented on SOLR-5981: - I'm not seeing this fix in the git mirror of luc

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980062#comment-13980062 ] ASF subversion and git services commented on SOLR-6011: --- Commit 15898

[jira] [Resolved] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler resolved LUCENE-5626. --- Resolution: Fixed Backported to 4.8 for respin. > SimpleFSLockFactory "access denied" on wi

[jira] [Commented] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980054#comment-13980054 ] ASF subversion and git services commented on LUCENE-5626: - Commit

[jira] [Created] (SOLR-6013) Fix method visibility of Evaluator, refactor DateFormatEvaluator for extensibility

Aaron LaBella created SOLR-6013: --- Summary: Fix method visibility of Evaluator, refactor DateFormatEvaluator for extensibility Key: SOLR-6013 URL: https://issues.apache.org/jira/browse/SOLR-6013 Project:

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980053#comment-13980053 ] Timothy Potter commented on SOLR-5473: -- Thought I'd add my 2 cents on this one as I've

[jira] [Updated] (SOLR-6013) Fix method visibility of Evaluator, refactor DateFormatEvaluator for extensibility

[ https://issues.apache.org/jira/browse/SOLR-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron LaBella updated SOLR-6013: Attachment: 0001-change-method-variable-visibility-and-refactor-for-extensibility.patch attaching t

[jira] [Commented] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980049#comment-13980049 ] ASF subversion and git services commented on LUCENE-5626: - Commit

[jira] [Commented] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980046#comment-13980046 ] ASF subversion and git services commented on LUCENE-5626: - Commit

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980037#comment-13980037 ] ASF subversion and git services commented on SOLR-6011: --- Commit 15898

[jira] [Commented] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980035#comment-13980035 ] ASF subversion and git services commented on LUCENE-5626: - Commit

[jira] [Updated] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-5626: -- Fix Version/s: 4.8 > SimpleFSLockFactory "access denied" on windows. > ---

[jira] [Reopened] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler reopened LUCENE-5626: --- As we respin 4.8, I will backport this one, too, because otherwise it could happen that somebod

[jira] [Updated] (LUCENE-5626) SimpleFSLockFactory "access denied" on windows.

[ https://issues.apache.org/jira/browse/LUCENE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-5626: -- Priority: Blocker (was: Major) > SimpleFSLockFactory "access denied" on windows. > --

Re: [VOTE] Lucene/Solr 4.8.0 RC1

On Thu, Apr 24, 2014 at 1:57 PM, Uwe Schindler wrote: > OK, > I'll wait for the fix. Is this a new bug in 4.8? OK, thanks. It's an old bug in Lucene, but a new bug in Solr (since complex phrase queries weren't exposed before). I'll commit now. -Yonik ---

[jira] [Updated] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-6011: Fix Version/s: 5.0 4.9 4.8 > inOrder does not work with the co

RE: [VOTE] Lucene/Solr 4.8.0 RC1

OK, I'll wait for the fix. Is this a new bug in 4.8? Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik > Seeley > Sent: Thursday, April

[jira] [Updated] (SOLR-5819) Investigate & reduce size of ref-guide PDF

[ https://issues.apache.org/jira/browse/SOLR-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-5819: --- Description: As noted on the solr-user mailing list in response to the ANNOUNCE about the 4.7 ref guide, the

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980013#comment-13980013 ] Noble Paul commented on SOLR-5473: -- bq.The external interface bq. I've already gone into a

[jira] [Commented] (SOLR-5819) Investigate & reduce size of ref-guide PDF

[ https://issues.apache.org/jira/browse/SOLR-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980009#comment-13980009 ] Hoss Man commented on SOLR-5819: Since the CWIKI upgrade still hasn't happened, i used rmui

Re: [VOTE] Lucene/Solr 4.8.0 RC1

I ran into a very serious bug during my manual testing of 4.8 that I think warrants a respin. https://issues.apache.org/jira/browse/SOLR-6011 In a normal Solr setup, incorrect results are returned from complex phrase queries if inOrder is ever changed for the same query. This would be maddening f

[jira] [Updated] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-6011: --- Attachment: SOLR-6011.patch OK, here's an updated patch that fixes the issue. > inOrder does not work

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979983#comment-13979983 ] Mark Miller commented on SOLR-5473: --- Thank you. bq. The idea of splitting the clustersta

[jira] [Commented] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979969#comment-13979969 ] Noble Paul commented on SOLR-5473: -- hi [~markrmil...@gmail.com] I'm work on a reverse pat

[jira] [Comment Edited] (SOLR-5473) Make one state.json per collection

[ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979969#comment-13979969 ] Noble Paul edited comment on SOLR-5473 at 4/24/14 5:13 PM: --- hi [~

[jira] [Updated] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-6011: --- Attachment: SOLR-6011.patch Here's a test that fails. I changed the testcase to not use separate sche

Re: 4.8 Solr Ref Guide Release Plan

: I'm still trying to document some stuff (async core admin calls) but I'm : having issues saving that stuff. : Once I'm able to save that, I should be done with everything that's on my : mind for 4.8 documentation. Yeah ... cwiki seems to be having some performance issues at the moment, so rele

[jira] [Commented] (SOLR-6011) inOrder does not work with the complexphrase parser

[ https://issues.apache.org/jira/browse/SOLR-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979944#comment-13979944 ] Ahmet Arslan commented on SOLR-6011: {code} {!complexphrase df=manu inOrder=true}"high*

Re: 4.8 Solr Ref Guide Release Plan

I'm still trying to document some stuff (async core admin calls) but I'm having issues saving that stuff. Once I'm able to save that, I should be done with everything that's on my mind for 4.8 documentation. On Wed, Apr 23, 2014 at 10:33 AM, Chris Hostetter wrote: > > : 2) I'll review the TODO l

Re: release votes

On Apr 24, 2014, at 8:07 AM, Thomas Koch wrote: > Hi Andi, > > I don't agree that it is unimportant to make PyLucene releases. Without a > ready-to-run software package the hurdles to use PyLucene are raised. It is > already not quite simple (for beginners) to install PyLucene on the various > pl

[jira] [Created] (SOLR-6012) Dutch language stemming issues

Ashokkumar Balasubramanian created SOLR-6012: Summary: Dutch language stemming issues Key: SOLR-6012 URL: https://issues.apache.org/jira/browse/SOLR-6012 Project: Solr Issue Type:

Re: svn commit: r1589782 - /lucene/dev/branches/branch_4x/lucene/core/src/test/org/apache/lucene/inde x/TestTerms.java

Yeah, I didn't want to disable the full test, just that one method, because I want Terms.getMin/Max testing for Lucene3x too. Would be nice if we could @SuppressCodecs for just one method ... I'll add a comment. Mike McCandless http://blog.mikemccandless.com On Thu, Apr 24, 2014 at 12:26 PM,

RE: svn commit: r1589782 - /lucene/dev/branches/branch_4x/lucene/core/src/test/org/apache/lucene/inde x/TestTerms.java

: Why not use the @SuppressCodes annotation? mike mentioned this in his reply to the jenkins failure... >> I committed a fix, disabling Lucene3x for that test case. I didn't >> use @SuppressCodecs because the other tests should work fine w/ >> Lucene3x. ..perhaps putting this in the test as a

RE: svn commit: r1589782 - /lucene/dev/branches/branch_4x/lucene/core/src/test/org/apache/lucene/index/TestTerms.java

Why not use the @SuppressCodes annotation? - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: mikemcc...@apache.org [mailto:mikemcc...@apache.org] > Sent: Thursday, April 24, 2014 6:08 PM > To: comm...@luce

[jira] [Comment Edited] (SOLR-2894) Implement distributed pivot faceting

[ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979898#comment-13979898 ] Brett Lucey edited comment on SOLR-2894 at 4/24/14 4:21 PM: And

[jira] [Comment Edited] (SOLR-2894) Implement distributed pivot faceting

[ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979898#comment-13979898 ] Brett Lucey edited comment on SOLR-2894 at 4/24/14 4:20 PM: And

  1   2   >