[JENKINS] Lucene-Solr-master-Linux (64bit/jdk1.8.0_102) - Build # 17618 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17618/ Java: 64bit/jdk1.8.0_102 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler Error Message: ObjectTracker found 1 object(s) that

[JENKINS] Lucene-Solr-Tests-master - Build # 1369 - Still unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1369/ 1 tests failed. FAILED: org.apache.solr.handler.TestReqParamsAPI.test Error Message: Could not get expected value 'null' for path 'response/params/y/p' full output: { "responseHeader":{ "status":0, "QTime":0},

Re: Lucene/Solr 6.2.0 release

On 20 August 2016 at 10:14, Steve Rowe wrote: > The usual thing for committers who have input on release notes is to directly > edit the wiki pages themselves. I guess I was not sure whether that's a correct phrasing and whether I can call my contribution 'large' given that

[JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_102) - Build # 17616 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17616/ Java: 32bit/jdk1.8.0_102 -server -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.LeaderFailoverAfterPartitionTest.test Error Message: org.apache.solr.client.solrj.SolrServerException: No live SolrServers

[JENKINS] Lucene-Solr-Tests-6.x - Build # 427 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/427/ 1 tests failed. FAILED: org.apache.solr.cloud.TestMiniSolrCloudCluster.testStopAllStartAll Error Message: Address already in use Stack Trace: java.net.BindException: Address already in use at

[JENKINS] Lucene-Solr-master-Windows (64bit/jdk1.8.0_102) - Build # 6063 - Still Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6063/ Java: 64bit/jdk1.8.0_102 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 3 tests failed. FAILED: org.apache.solr.common.cloud.TestCollectionStateWatchers.testSimpleCollectionWatch Error Message: Stack Trace:

Re: Is precisionStep stuff still useful with docValues?

> On 20 August 2016 at 02:24, Michael McCandless > wrote: >> You should use dimensional points for range searching now. On Fri, Aug 19, 2016 at 7:56 PM, Alexandre Rafalovitch wrote: > How would I do that? Solr does not currently have support. See

Re: Lucene/Solr 6.2.0 release

Hi Alex, The usual thing for committers who have input on release notes is to directly edit the wiki pages themselves. Solr has its own clone of Lucene’s query parser (with some syntax additions), and I haven’t finished making the whitespace changes for it yet (SOLR-9185), so Solr won’t be

Re: Is precisionStep stuff still useful with docValues?

How would I do that? Here is the current definition of the field: I can see that under the covers it makes a choice between DocValues and LegacyNumericRangeQuery based on whether the field is indexed. So, do I use a different non-Trie type for this range use-case? I did a quick search

Re: Lucene/Solr 6.2.0 release

For my Solr's work, I think it is safe to summarize them as "A (large?) number of regressions were fixed in the new Admin UI". For Lucene's "QueryParser can now be told to not pre-split on whitespace" - it would be good to highlight it somewhere very clearly on the Solr side. Not sure what the

[JENKINS] Lucene-Solr-Tests-master - Build # 1368 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1368/ 2 tests failed. FAILED: org.apache.solr.cloud.LeaderFailoverAfterPartitionTest.test Error Message: No live SolrServers available to handle this request:[http://127.0.0.1:36835/c8n_1x3_lf_shard1_replica3] Stack Trace:

Re: Lucene/Solr 6.2.0 release

OK I cut the release branch (branch_6_2), and started a draft of Lucene's release notes: https://wiki.apache.org/lucene-java/ReleaseNote62 And Solr's: https://wiki.apache.org/solr/ReleaseNote62 If someone could especially help out w/ Solr's that would be nice. I'll make my way through

[JENKINS] Lucene-Solr-Tests-6.x - Build # 426 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/426/ 3 tests failed. FAILED: org.apache.solr.core.TestDynamicLoading.testDynamicLoading Error Message: Could not get expected value 'X val' for path 'x' full output: { "responseHeader":{ "status":0, "QTime":0},

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 794 - Still Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/794/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: org.apache.solr.handler.component.SpellCheckComponentTest.test Error Message: List size mismatch @ spellcheck/suggestions Stack Trace:

[JENKINS] Lucene-Solr-Tests-master - Build # 1367 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1367/ 1 tests failed. FAILED: org.apache.solr.cloud.TestTolerantUpdateProcessorCloud.testVariousAddsViaShard2NonLeaderClient Error Message: Could not load collection from ZK: test_col Stack Trace:

[JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_102) - Build # 17614 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17614/ Java: 32bit/jdk1.8.0_102 -server -XX:+UseG1GC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler Error Message: ObjectTracker found 1 object(s) that were not released!!!

[jira] [Commented] (SOLR-9412) Update Macro Expander for replacement logic

[ https://issues.apache.org/jira/browse/SOLR-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428708#comment-15428708 ] Yonik Seeley commented on SOLR-9412: +1 to the idea, and to the latest patch. > Update Macro Expander

[jira] [Commented] (SOLR-9412) Update Macro Expander for replacement logic

[ https://issues.apache.org/jira/browse/SOLR-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428693#comment-15428693 ] Jon Dorando commented on SOLR-9412: --- This is really good! Thanks for the suggestions! :) > Update Macro

[jira] [Updated] (SOLR-9412) Update Macro Expander for replacement logic

[ https://issues.apache.org/jira/browse/SOLR-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Dorando updated SOLR-9412: -- Attachment: (was: test_macro_expander.patch) > Update Macro Expander for replacement logic >

[JENKINS-EA] Lucene-Solr-6.x-Linux (64bit/jdk-9-ea+131) - Build # 1519 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/1519/ Java: 64bit/jdk-9-ea+131 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.TestMiniSolrCloudCluster.testStopAllStartAll Error Message: Address already in use Stack Trace:

Re: Proposal to Move Solr Ref Guide off Confluence

Thanks for taking time for looking at these options Casandra. I specially agree with the third of the painful points you mentioned, the fact that we can't maintain online documentation for different versions. I like that we have a released PDF version for every minor version, but 99.9% of the time

Re: Proposal to Move Solr Ref Guide off Confluence

On 8/19/2016 11:23 AM, Chris Hostetter wrote: > To be very clear, my point was that by moving out of confluence and to an > asciidoc based system kept in git, we know have the *choice* to > maintain/backport documentation for multiple versions, and an easy way to > backport changes. > > This is

Re: Is precisionStep stuff still useful with docValues?

Perhaps then something other than "configuration" -- perhaps some request param flag -- I dunno. But it's too easy to shoot yourself in the foot. I'm glad we have the feature/capability though. On Fri, Aug 19, 2016 at 12:46 PM Yonik Seeley wrote: > On Fri, Aug 19, 2016 at

[JENKINS] Lucene-Solr-SmokeRelease-master - Build # 570 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/570/ No tests ran. Build Log: [...truncated 40608 lines...] prepare-release-no-sign: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/lucene/build/smokeTestRelease/dist [copy]

Re: Is precisionStep stuff still useful with docValues?

: +1, we should remove the Lucene doc values based queries. Whoa... Wouldn't that completley kill ~50% of the utility of having updatedable DocValues support in Lucene? Having an updatable field you can sort on is handy, but if the only way to search/filter on the same effective (updated)

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3490 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3490/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.HttpPartitionTest.test Error Message: The partitioned replica did not get marked down expected:<[down]> but

Re: Proposal to Move Solr Ref Guide off Confluence

: I am not against having multiple documentation branches -- I am *for* : that. I am against emulating our current source code practice of needing : to commit twice (two branches) for most things. I think that should be the : exception, not the rule. Only during a new dot-zero release would we

[jira] [Comment Edited] (SOLR-9415) graph search filter edge

[ https://issues.apache.org/jira/browse/SOLR-9415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428480#comment-15428480 ] Kevin Watters edited comment on SOLR-9415 at 8/19/16 5:20 PM: -- Hello cmd,

[jira] [Commented] (SOLR-9415) graph search filter edge

[ https://issues.apache.org/jira/browse/SOLR-9415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428480#comment-15428480 ] Kevin Watters commented on SOLR-9415: - Hello cmd, Are you using the GraphQueryParser? If so, you can

Re: Is precisionStep stuff still useful with docValues?

On Fri, Aug 19, 2016 at 12:17 PM, David Smiley wrote: > I think it's a bad thing that we let you do queries on a field with > docValues that has no index *by default* -- i.e. without some field type > attribute where you expressly allow it because you know what you're

[JENKINS] Lucene-Solr-Tests-master - Build # 1366 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1366/ 1 tests failed. FAILED: org.apache.solr.security.BasicAuthIntegrationTest.testBasics Error Message: IOException occured when talking to server at: http://127.0.0.1:33282/solr/testSolrCloudCollection_shard1_replica2 Stack

Re: Is precisionStep stuff still useful with docValues?

Just like Michael: +1, we should remove the Lucene doc values based queries. yeah, I've seen people do this too (search non-indexed DV fields). It performs fine on the techproducts data set... all 32 docs Just enough to encourage people think it's OK until they try to scale. Erick On Fri,

Re: Is precisionStep stuff still useful with docValues?

You should use dimensional points for range searching now. Mike McCandless http://blog.mikemccandless.com On Fri, Aug 19, 2016 at 12:02 PM, Alexandre Rafalovitch wrote: > Hi, > > I was looking at the type definitions in our examples and we have > numerics with

Re: Is precisionStep stuff still useful with docValues?

+1, we should remove the Lucene doc values based queries. Mike McCandless http://blog.mikemccandless.com On Fri, Aug 19, 2016 at 12:17 PM, David Smiley wrote: > Alex, > > ... ok Yonik beet me to it. But any way, the index structure & the > docValues structure are

Re: Is precisionStep stuff still useful with docValues?

Alex, ... ok Yonik beet me to it. But any way, the index structure & the docValues structure are dramatically different for very different use-cases. I think it's a bad thing that we let you do queries on a field with docValues that has no index *by default* -- i.e. without some field type

Re: Is precisionStep stuff still useful with docValues?

On Fri, Aug 19, 2016 at 12:02 PM, Alexandre Rafalovitch wrote: > But the > documentation that explains why the later are useful > (NumericRangeQuery) is now a (LegacyNumericRangeQuery) and the source > code seems to show that docValues can (should?) be used instead. Using

Re: Proposal to Move Solr Ref Guide off Confluence

I am not against having multiple documentation branches -- I am *for* that. I am against emulating our current source code practice of needing to commit twice (two branches) for most things. I think that should be the exception, not the rule. Only during a new dot-zero release would we be

Is precisionStep stuff still useful with docValues?

Hi, I was looking at the type definitions in our examples and we have numerics with precisionStep=0 and those with precisionStep=8. But the documentation that explains why the later are useful (NumericRangeQuery) is now a (LegacyNumericRangeQuery) and the source code seems to show that docValues

[JENKINS] Lucene-Solr-6.x-Windows (64bit/jdk1.8.0_102) - Build # 398 - Still Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Windows/398/ Java: 64bit/jdk1.8.0_102 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.schema.TestManagedSchemaAPI Error Message: ObjectTracker found 10 object(s) that were not

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428334#comment-15428334 ] Robert Muir commented on LUCENE-7419: - thanks [~mikemccand] for tracking this down! > performance

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

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

[jira] [Resolved] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-7419. - Resolution: Fixed > performance bug in tokenstream.end() >

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

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

Re: Proposal to Move Solr Ref Guide off Confluence

On Thu, Aug 18, 2016 at 10:38 PM, Erick Erickson wrote: > > The other question I have is how to find the file I want to edit. I'm > taking it on faith that there's a way to find a particular asciidoc > file without resorting to a recursive grep, but if not I can cope with

Re: Proposal to Move Solr Ref Guide off Confluence

On Thu, Aug 18, 2016 at 8:48 PM, David Smiley wrote: > Ugh! I think it's a PITA that we basically always back-port all commits to > another branch, and the prospect of having to do this to documentation as > well will add a large barrier to editing the docs. I propose

[jira] [Commented] (SOLR-9424) Deleting is not happening in solr 5.4.1 with Manifold CF For Sharepoint

[ https://issues.apache.org/jira/browse/SOLR-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428301#comment-15428301 ] Erick Erickson commented on SOLR-9424: -- This is probably better raised on the user's list first, we

[jira] [Commented] (SOLR-9412) Update Macro Expander for replacement logic

[ https://issues.apache.org/jira/browse/SOLR-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428298#comment-15428298 ] Christine Poerschke commented on SOLR-9412: --- re: the random(ized) elements in the test and

[jira] [Updated] (SOLR-9412) Update Macro Expander for replacement logic

[ https://issues.apache.org/jira/browse/SOLR-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-9412: -- Attachment: SOLR-9412.patch Hi Jon, thanks for your patch. Please find attached some

[jira] [Commented] (SOLR-9319) DELETEREPLICA should be able to accept just count and remove replicas intelligenty

[ https://issues.apache.org/jira/browse/SOLR-9319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428268#comment-15428268 ] Nitin Sharma commented on SOLR-9319: It is already rebased on top of current master. Did you mean

[jira] [Updated] (SOLR-9424) Deleting is not happening in solr 5.4.1 with Manifold CF For Sharepoint

[ https://issues.apache.org/jira/browse/SOLR-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] soundarya g updated SOLR-9424: -- Summary: Deleting is not happening in solr 5.4.1 with Manifold CF For Sharepoint (was: Deleting is not

[jira] [Commented] (LUCENE-7418) remove legacy numerics from join/ and queryparser/

[ https://issues.apache.org/jira/browse/LUCENE-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428255#comment-15428255 ] Michael McCandless commented on LUCENE-7418: +1 > remove legacy numerics from join/ and

[jira] [Updated] (SOLR-9310) PeerSync fails on a node restart due to IndexFingerPrint mismatch

[ https://issues.apache.org/jira/browse/SOLR-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pushkar Raste updated SOLR-9310: Attachment: SOLR-9310_final.patch Final patch. Here are highlights about the changes * Don't buffer

[jira] [Commented] (SOLR-9421) Refactor OverseerMessageHandler and make smaller classes

[ https://issues.apache.org/jira/browse/SOLR-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428236#comment-15428236 ] David Smiley commented on SOLR-9421: [~noble.paul] can you add a package for all these classes? It

[jira] [Commented] (SOLR-8644) ArrayIndexOutOfBoundsException in BlockJoinFieldFacetAccumulator

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

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428224#comment-15428224 ] David Smiley commented on LUCENE-7419: -- Nice; +1 to the patch and to commit to v6.2 > performance

[jira] [Commented] (SOLR-8644) ArrayIndexOutOfBoundsException in BlockJoinFieldFacetAccumulator

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

[jira] [Created] (SOLR-9424) Deleting is not happening in solr 5.4.1

soundarya g created SOLR-9424: - Summary: Deleting is not happening in solr 5.4.1 Key: SOLR-9424 URL: https://issues.apache.org/jira/browse/SOLR-9424 Project: Solr Issue Type: Bug Security

[JENKINS] Lucene-Solr-master-Windows (64bit/jdk1.8.0_102) - Build # 6062 - Still Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6062/ Java: 64bit/jdk1.8.0_102 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 4 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.schema.TestManagedSchemaAPI Error Message: ObjectTracker found 10 object(s) that were

[jira] [Updated] (SOLR-8644) ArrayIndexOutOfBoundsException in BlockJoinFieldFacetAccumulator

[ https://issues.apache.org/jira/browse/SOLR-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-8644: --- Attachment: SOLR-8644.patch > ArrayIndexOutOfBoundsException in BlockJoinFieldFacetAccumulator

[jira] [Commented] (SOLR-9215) QT parameter doesn't appear to function anymore

[ https://issues.apache.org/jira/browse/SOLR-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428195#comment-15428195 ] Shawn Heisey commented on SOLR-9215: bq. Confusing things a little is SolrJ... you can specify the

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428185#comment-15428185 ] Michael McCandless commented on LUCENE-7419: I tested indexing all geonames, using lucene

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428181#comment-15428181 ] Robert Muir commented on LUCENE-7419: - As soon as mike pointed to this area of the code being

[jira] [Updated] (SOLR-8643) remove BlockJoinFacetComponent; was: UnsupportedOperationException in FakeScorer

[ https://issues.apache.org/jira/browse/SOLR-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-8643: --- Fix Version/s: (was: 6.0) (was: 5.5) master (7.0)

[jira] [Commented] (SOLR-8643) remove BlockJoinFacetComponent; was: UnsupportedOperationException in FakeScorer

[ https://issues.apache.org/jira/browse/SOLR-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428154#comment-15428154 ] Mikhail Khludnev commented on SOLR-8643: followup CHANGES.txt fix

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428142#comment-15428142 ] Adrien Grand commented on LUCENE-7419: -- I was just curious to understand whit made hotspot unhappy

[jira] [Commented] (SOLR-8643) remove BlockJoinFacetComponent; was: UnsupportedOperationException in FakeScorer

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

[jira] [Commented] (LUCENE-7412) TestGeo3DPoint.testGeo3DRelations test failure

[ https://issues.apache.org/jira/browse/LUCENE-7412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428098#comment-15428098 ] Karl Wright commented on LUCENE-7412: - Ok, looking at the composite polygon in question, there is no

[jira] [Resolved] (SOLR-9391) LBHttpSolrClient.request can return incorrect Rsp.server string

[ https://issues.apache.org/jira/browse/SOLR-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke resolved SOLR-9391. --- Resolution: Fixed Fix Version/s: 6.x master (7.0) >

[jira] [Updated] (SOLR-5725) Efficient facets without counts for enum method

[ https://issues.apache.org/jira/browse/SOLR-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radoslaw Zielinski updated SOLR-5725: - Attachment: SOLR-5725-master.patch I've altered the patch to be applicable on the current

[jira] [Commented] (SOLR-9391) LBHttpSolrClient.request can return incorrect Rsp.server string

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

[jira] [Commented] (LUCENE-7420) SpanishLightStemmer stemming errors

[ https://issues.apache.org/jira/browse/LUCENE-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428029#comment-15428029 ] J Pardos commented on LUCENE-7420: -- I see. I understand these stemmers are not perfect; I just proposed

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427997#comment-15427997 ] Robert Muir commented on LUCENE-7419: - I am sure the problem originated when factoring lots of +1/-1

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427993#comment-15427993 ] Uwe Schindler commented on LUCENE-7419: --- I agree, the latest patch is the only correct fix. The

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 793 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/793/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseG1GC 4 tests failed. FAILED: org.apache.solr.cloud.ForceLeaderTest.testReplicasInLIRNoLeader Error Message: No live SolrServers available to handle this

[jira] [Commented] (SOLR-9319) DELETEREPLICA should be able to accept just count and remove replicas intelligenty

[ https://issues.apache.org/jira/browse/SOLR-9319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427981#comment-15427981 ] Noble Paul commented on SOLR-9319: -- Can you just update the patch to the current trunk > DELETEREPLICA

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427979#comment-15427979 ] Robert Muir commented on LUCENE-7419: - That's not the issue as I see it. To me, the problem is that

[jira] [Commented] (LUCENE-7420) SpanishLightStemmer stemming errors

[ https://issues.apache.org/jira/browse/LUCENE-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427968#comment-15427968 ] Robert Muir commented on LUCENE-7420: - None of these stemmers are 100%. We simply implement the logic

[jira] [Commented] (SOLR-9391) LBHttpSolrClient.request can return incorrect Rsp.server string

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

[JENKINS-EA] Lucene-Solr-6.x-Linux (32bit/jdk-9-ea+131) - Build # 1515 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/1515/ Java: 32bit/jdk-9-ea+131 -server -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.handler.TestReqParamsAPI.test Error Message: Could not get expected value 'CY val' for path 'params/c' full output: {

[jira] [Commented] (LUCENE-7420) SpanishLightStemmer stemming errors

[ https://issues.apache.org/jira/browse/LUCENE-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427888#comment-15427888 ] J Pardos commented on LUCENE-7420: -- The attached patch stems four character words not ending in 's'. >

[jira] [Updated] (LUCENE-7420) SpanishLightStemmer stemming errors

[ https://issues.apache.org/jira/browse/LUCENE-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J Pardos updated LUCENE-7420: - Attachment: SpanishLightStemmer.java.patch > SpanishLightStemmer stemming errors >

[jira] [Created] (LUCENE-7420) SpanishLightStemmer stemming errors

J Pardos created LUCENE-7420: Summary: SpanishLightStemmer stemming errors Key: LUCENE-7420 URL: https://issues.apache.org/jira/browse/LUCENE-7420 Project: Lucene - Core Issue Type: Bug

[JENKINS] Lucene-Solr-6.x-MacOSX (64bit/jdk1.8.0) - Build # 357 - Unstable!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-MacOSX/357/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.core.TestArbitraryIndexDir.testLoadNewIndexDir Error Message: Exception during query Stack Trace: java.lang.RuntimeException:

[jira] [Commented] (LUCENE-7418) remove legacy numerics from join/ and queryparser/

[ https://issues.apache.org/jira/browse/LUCENE-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427829#comment-15427829 ] Martijn van Groningen commented on LUCENE-7418: --- +1 to the changes in join > remove legacy

[jira] [Commented] (LUCENE-7419) performance bug in tokenstream.end()

[ https://issues.apache.org/jira/browse/LUCENE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427806#comment-15427806 ] Adrien Grand commented on LUCENE-7419: -- So if I understand correctly, the slow down was caused by

RE: Lucene/Solr Nightly Tests Master Build #1100 stuck?

Hi, I talked with Steve via IRC yesterday. > This job finally finished. > > Looks like the full disk problem was triggered when writing logs out - the > following is recorded in consoleText 1,478 times: > > - > [junit4] java.io.IOException: No space left on device >[junit4] at

[jira] [Updated] (SOLR-8643) remove BlockJoinFacetComponent; was: UnsupportedOperationException in FakeScorer

[ https://issues.apache.org/jira/browse/SOLR-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-8643: --- Attachment: SOLR-8643.patch the patch makes {{BlockJoinFacetComponent}} just an empty subclass