[JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 3046 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/3046/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.update.AutoCommitTest.testCommitWithin Error Message: Exception during query Stack Trace: java.lang.RuntimeException:

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122707#comment-15122707 ] Anshum Gupta commented on SOLR-8619: What I have in mind should play nice with both of those things

[jira] [Commented] (SOLR-8606) Duplicate tokens using WordDelimiterFilter for a specific configuration

[ https://issues.apache.org/jira/browse/SOLR-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122541#comment-15122541 ] Erik Hatcher commented on SOLR-8606: The RemoveDuplicatesTokenFilter would remove one of those

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122538#comment-15122538 ] Mark Miller commented on SOLR-8619: --- bq. 1. Reject an ADDREPLICA call if all current replicas for the

[JENKINS] Lucene-Solr-5.x-Linux (32bit/jdk1.7.0_80) - Build # 15387 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15387/ Java: 32bit/jdk1.7.0_80 -client -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: Stack Trace: java.lang.AssertionError at

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122520#comment-15122520 ] Erick Erickson commented on SOLR-8619: -- I'd also not want to even _try_ to ADDREPLICA if there were no

[jira] [Commented] (SOLR-8606) Duplicate tokens using WordDelimiterFilter for a specific configuration

[ https://issues.apache.org/jira/browse/SOLR-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122672#comment-15122672 ] Shawn Heisey commented on SOLR-8606: When I read the description of the RemoveDuplicates filter on the

RE: [JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 3044 - Failure!

Hi, this one scares me a bit: Last night I updated the JVM versions on Policeman Jenkins. This also updated MacOSX to Java 8u72 (from 8u66). I tried to reproduce (ant beast -Dbeast.iters=100) with this seed locally with 8u60 and also 8u72 -> no luck. Does anybody have an idea what the cause

[jira] [Updated] (LUCENE-6998) We should detect truncation for all index files

[ https://issues.apache.org/jira/browse/LUCENE-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6998: --- Attachment: LUCENE-6998.patch Another iteration, I think it's ready. I added two

[JENKINS] Lucene-Solr-trunk-Solaris (64bit/jdk1.8.0) - Build # 362 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/362/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestStressReplication Error Message: timed out waiting for collection1 startAt time to exceed:

RE: [JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+102) - Build # 15679 - Failure!

Hi, I am also afraid, because we had 3 failures in approx 2 hours. I updated JDK 9 to b102 today at 1:00 UTC, so 8 hours ago and those 3 runs were the only ones with Java 9. As this was a bigger update (usual Windows update hell, Slowlaris update hell, Linux kernel updates), I triggered a full

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121365#comment-15121365 ] Joel Bernstein commented on SOLR-8602: -- I was just reviewing the exception handling in ResultSetImpl

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121375#comment-15121375 ] Joel Bernstein commented on SOLR-8602: -- Doing some more review. That particular exception would have

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121417#comment-15121417 ] Kevin Risden commented on SOLR-8602: The issue was that there was no exception added to the

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121356#comment-15121356 ] Joel Bernstein commented on SOLR-8602: -- There are lot's of inconsistencies between limited and

[jira] [Commented] (SOLR-7981) term based ValueSourceParsers should support an option to run an analyzer for hte specified field on the input

[ https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121408#comment-15121408 ] Jason Gerlowski commented on SOLR-7981: --- Ah, I see. The "newdev" label is actually what initially

[jira] [Updated] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8602: --- Attachment: SOLR-8602.patch Improve exception handling so that the underlying exception is thrown

[jira] [Commented] (SOLR-7981) term based ValueSourceParsers should support an option to run an analyzer for hte specified field on the input

[ https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121304#comment-15121304 ] Shashank Tyagi commented on SOLR-7981: -- Hi Jason, I just looking to something to contribute to

Why lucene is too fast

Hello Everyone, I am asking a simple question why Lucene is too fast, if I take the example of mysql index, its behind binary tree algorithms. Which algorithms Lucene used in the background ? or Please suggest me any link for proper lucene understanding internal architecture art from

[jira] [Assigned] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

[ https://issues.apache.org/jira/browse/LUCENE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-6999: -- Assignee: Michael McCandless > Lucene60PointsWriter has a buggy close method

[jira] [Commented] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

[ https://issues.apache.org/jira/browse/LUCENE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121131#comment-15121131 ] Michael McCandless commented on LUCENE-6999: Thanks Rob, I'll add heroic exception handling

[jira] [Commented] (SOLR-8371) Try and prevent too many recovery requests from stacking up and clean up some faulty logic.

[ https://issues.apache.org/jira/browse/SOLR-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121133#comment-15121133 ] Stephan Lagraulet commented on SOLR-8371: - Can you update Fix Version to 5.5 if it is going to be

[jira] [Updated] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

[ https://issues.apache.org/jira/browse/LUCENE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6999: --- Fix Version/s: 6.0 Trunk > Lucene60PointsWriter has a buggy close

[jira] [Commented] (SOLR-8610) DIH - Resolve variables in encryptKeyFile

[ https://issues.apache.org/jira/browse/SOLR-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121254#comment-15121254 ] Kristine Jetzke commented on SOLR-8610: --- See attached patch for change. > DIH - Resolve variables in

[jira] [Comment Edited] (SOLR-2199) DIH JdbcDataSource - Support multiple resultsets

[ https://issues.apache.org/jira/browse/SOLR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121257#comment-15121257 ] Kristine Jetzke edited comment on SOLR-2199 at 1/28/16 11:42 AM: - Any

[jira] [Created] (SOLR-8611) Incorrect logging in ZkController

Stephan Lagraulet created SOLR-8611: --- Summary: Incorrect logging in ZkController Key: SOLR-8611 URL: https://issues.apache.org/jira/browse/SOLR-8611 Project: Solr Issue Type: Bug

[jira] [Commented] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

[ https://issues.apache.org/jira/browse/LUCENE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121262#comment-15121262 ] Robert Muir commented on LUCENE-6999: - +1 > Lucene60PointsWriter has a buggy close method >

[jira] [Created] (SOLR-8610) DIH - Resolve variables in encryptKeyFile

Kristine Jetzke created SOLR-8610: - Summary: DIH - Resolve variables in encryptKeyFile Key: SOLR-8610 URL: https://issues.apache.org/jira/browse/SOLR-8610 Project: Solr Issue Type:

[jira] [Commented] (SOLR-7940) [CollectionAPI] Frequent Cluster Status timeout

[ https://issues.apache.org/jira/browse/SOLR-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121155#comment-15121155 ] Stephan Lagraulet commented on SOLR-7940: - It looks fixed on my 5.4 version > [CollectionAPI]

[jira] [Updated] (SOLR-7940) [CollectionAPI] Frequent Cluster Status timeout

[ https://issues.apache.org/jira/browse/SOLR-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Lagraulet updated SOLR-7940: Fix Version/s: 5.3 Probably fixed by SOLR-7636 > [CollectionAPI] Frequent Cluster Status

[jira] [Updated] (SOLR-8610) DIH - Resolve variables in encryptKeyFile

[ https://issues.apache.org/jira/browse/SOLR-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Jetzke updated SOLR-8610: -- Attachment: SOLR-8610.patch > DIH - Resolve variables in encryptKeyFile >

[jira] [Updated] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

[ https://issues.apache.org/jira/browse/LUCENE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6999: --- Attachment: LUCENE-6999.patch Here's a patch, folding in [~rcmuir]'s test changes,

[jira] [Updated] (LUCENE-6750) TestMergeSchedulerExternal failure

[ https://issues.apache.org/jira/browse/LUCENE-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-6750: -- Affects Version/s: 5.x > TestMergeSchedulerExternal failure >

[jira] [Commented] (SOLR-7121) Solr nodes should go down based on configurable thresholds and not rely on resource exhaustion

[ https://issues.apache.org/jira/browse/SOLR-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121255#comment-15121255 ] Stephan Lagraulet commented on SOLR-7121: - Any updates on this issue? As there is work done by

[jira] [Commented] (LUCENE-6998) We should detect truncation for all index files

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

[jira] [Updated] (SOLR-8610) DIH - Resolve variables in encryptKeyFile

[ https://issues.apache.org/jira/browse/SOLR-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Jetzke updated SOLR-8610: -- Description: I would like to use a variable like {{$\{path.to.file\}}} for {{encryptKeyFile}}

[jira] [Resolved] (SOLR-7940) [CollectionAPI] Frequent Cluster Status timeout

[ https://issues.apache.org/jira/browse/SOLR-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Lagraulet resolved SOLR-7940. - Resolution: Fixed > [CollectionAPI] Frequent Cluster Status timeout >

[jira] [Updated] (SOLR-8610) DIH - Resolve variables in encryptKeyFile

[ https://issues.apache.org/jira/browse/SOLR-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Jetzke updated SOLR-8610: -- Description: I would like to use a variable like {{$\{path.to.file\}}} for {{encryptKeyFile}}

[jira] [Commented] (LUCENE-6998) We should detect truncation for all index files

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

[jira] [Resolved] (LUCENE-6998) We should detect truncation for all index files

[ https://issues.apache.org/jira/browse/LUCENE-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-6998. Resolution: Fixed > We should detect truncation for all index files >

[jira] [Commented] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

[ https://issues.apache.org/jira/browse/LUCENE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121194#comment-15121194 ] Uwe Schindler commented on LUCENE-6999: --- Looks better, like it! > Lucene60PointsWriter has a buggy

[jira] [Commented] (LUCENE-6750) TestMergeSchedulerExternal failure

[ https://issues.apache.org/jira/browse/LUCENE-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121238#comment-15121238 ] Uwe Schindler commented on LUCENE-6750: --- Happened last night again. I was afraid that this was new

[JENKINS] Lucene-Solr-5.x-Solaris (multiarch/jdk1.7.0) - Build # 356 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/356/ Java: multiarch/jdk1.7.0 -d32 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.core.TestArbitraryIndexDir.testLoadNewIndexDir Error Message: Exception during query Stack Trace: java.lang.RuntimeException:

Re: [JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 3044 - Failure!

This failure has been happening for a very long time now, only on OS X. It doesn't repro and it is scary! Steve opened an issue for it: https://issues.apache.org/jira/browse/LUCENE-6750 Mike McCandless http://blog.mikemccandless.com On Thu, Jan 28, 2016 at 3:59 AM, Uwe Schindler

[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

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

[jira] [Commented] (SOLR-2199) DIH JdbcDataSource - Support multiple resultsets

[ https://issues.apache.org/jira/browse/SOLR-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121257#comment-15121257 ] Kristine Jetzke commented on SOLR-2199: --- Any chance of this patch being applied soon? If there is

[jira] [Created] (SOLR-8612) DIH JdbcDataSource - statement not always closed

Kristine Jetzke created SOLR-8612: - Summary: DIH JdbcDataSource - statement not always closed Key: SOLR-8612 URL: https://issues.apache.org/jira/browse/SOLR-8612 Project: Solr Issue Type:

[jira] [Commented] (SOLR-8612) DIH JdbcDataSource - statement not always closed

[ https://issues.apache.org/jira/browse/SOLR-8612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121276#comment-15121276 ] Kristine Jetzke commented on SOLR-8612: --- I attached a patch fixing the mentioned issues. It also

[jira] [Updated] (SOLR-8612) DIH JdbcDataSource - statement not always closed

[ https://issues.apache.org/jira/browse/SOLR-8612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Jetzke updated SOLR-8612: -- Attachment: SOLR-8612.patch > DIH JdbcDataSource - statement not always closed >

[jira] [Commented] (SOLR-8597) add default, no-op QParserPlugin.init(NamedList) method

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

[jira] [Created] (SOLR-8617) Add a wait for active option in to add replica

Varun Thacker created SOLR-8617: --- Summary: Add a wait for active option in to add replica Key: SOLR-8617 URL: https://issues.apache.org/jira/browse/SOLR-8617 Project: Solr Issue Type: New

[JENKINS] Lucene-Solr-trunk-Solaris (64bit/jdk1.8.0) - Build # 363 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/363/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC 2 tests failed. FAILED: org.apache.solr.update.AutoCommitTest.testCommitWithin Error Message: Exception during query Stack Trace: java.lang.RuntimeException:

[jira] [Commented] (SOLR-8607) The Schema API refuses to add new fields that match existing dynamic fields

[ https://issues.apache.org/jira/browse/SOLR-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122751#comment-15122751 ] Steve Rowe commented on SOLR-8607: -- This workaround allowed me to create the {{new_txt}} field: first

[jira] [Comment Edited] (SOLR-8607) The Schema API refuses to add new fields that match existing dynamic fields

[ https://issues.apache.org/jira/browse/SOLR-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122720#comment-15122720 ] Steve Rowe edited comment on SOLR-8607 at 1/29/16 2:08 AM: --- I see this same

[jira] [Commented] (LUCENE-6997) Graduate GeoUtils and postings based GeoPointField from sandbox...

[ https://issues.apache.org/jira/browse/LUCENE-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121580#comment-15121580 ] Uwe Schindler commented on LUCENE-6997: --- What does this have to do with Java 9? > Graduate

[jira] [Commented] (LUCENE-6997) Graduate GeoUtils and postings based GeoPointField from sandbox...

[ https://issues.apache.org/jira/browse/LUCENE-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121593#comment-15121593 ] Uwe Schindler commented on LUCENE-6997: --- Optional dependencies in Maven have nothing to do with

[jira] [Comment Edited] (LUCENE-6997) Graduate GeoUtils and postings based GeoPointField from sandbox...

[ https://issues.apache.org/jira/browse/LUCENE-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121593#comment-15121593 ] Uwe Schindler edited comment on LUCENE-6997 at 1/28/16 2:41 PM: Optional

[jira] [Comment Edited] (LUCENE-6997) Graduate GeoUtils and postings based GeoPointField from sandbox...

[ https://issues.apache.org/jira/browse/LUCENE-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121593#comment-15121593 ] Uwe Schindler edited comment on LUCENE-6997 at 1/28/16 2:43 PM: Optional

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121460#comment-15121460 ] Joel Bernstein commented on SOLR-8602: -- What was the change in this patch? > Implement

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121497#comment-15121497 ] Kevin Risden commented on SOLR-8602: H guess I had changed it already. I also consolidated the

"newdev" Label Reminder

Hi all, Just wanted to remind everyone of the "newdev" label, which is used to identify JIRA tasks appropriate for new/inexperienced Solr contributors. I was reminded of this after a conversation on SOLR-7981, when a prospective contributor shared a bit of frustration with the "newdev" list. A

[jira] [Commented] (SOLR-8613) SolrJ JDBC - SQL queries with limit do not fail when a bad column is provided

[ https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121502#comment-15121502 ] Kevin Risden commented on SOLR-8613: This isn't requires for SOLR-8502, but just added there to keep

Re: Why lucene is too fast

On 1/28/2016 6:21 AM, Mugeesh Husain wrote: > I am asking a simple question why Lucene is too fast, if I take the example > of mysql index, its behind binary tree algorithms. > > Which algorithms Lucene used in the background ? > > or Please suggest me any link for proper lucene understanding

[jira] [Commented] (LUCENE-6997) Graduate GeoUtils and postings based GeoPointField from sandbox...

[ https://issues.apache.org/jira/browse/LUCENE-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121528#comment-15121528 ] David Smiley commented on LUCENE-6997: -- bq. I agree. While the GeoUtils API is really close to being

[jira] [Created] (SOLR-8614) Add simple SolrClient.setUseXmlFormat

David Smiley created SOLR-8614: -- Summary: Add simple SolrClient.setUseXmlFormat Key: SOLR-8614 URL: https://issues.apache.org/jira/browse/SOLR-8614 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-8607) The Schema API refuses to add new fields that match existing dynamic fields

[ https://issues.apache.org/jira/browse/SOLR-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-8607: - Summary: The Schema API refuses to add new fields that match existing dynamic fields (was: In Managed

[jira] [Updated] (SOLR-8607) The Schema API refuses to add new fields that match existing dynamic fields

[ https://issues.apache.org/jira/browse/SOLR-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-8607: - Component/s: (was: Data-driven Schema) Schema and Analysis > The Schema API refuses

[jira] [Comment Edited] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122781#comment-15122781 ] Jason Gerlowski edited comment on SOLR-8619 at 1/29/16 2:22 AM: Throwing in

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122860#comment-15122860 ] Mark Miller commented on SOLR-8619: --- bq. Sure, I strongly think we need to be intelligent in electing

[jira] [Comment Edited] (SOLR-8586) Implement hash over all documents to check for shard synchronization

[ https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122872#comment-15122872 ] Joel Bernstein edited comment on SOLR-8586 at 1/29/16 3:18 AM: --- This is

[jira] [Commented] (SOLR-8586) Implement hash over all documents to check for shard synchronization

[ https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122872#comment-15122872 ] Joel Bernstein commented on SOLR-8586: -- This exactly what we need for implementing alerts (SOLR-8577).

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122882#comment-15122882 ] Erick Erickson commented on SOLR-8619: -- Perhaps a new state? "new"? "never_syncd"?

[jira] [Commented] (SOLR-8607) In Managed schema mode, Schema API throws error when adding new fields if the all catch dynamic field is defined

[ https://issues.apache.org/jira/browse/SOLR-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122720#comment-15122720 ] Steve Rowe commented on SOLR-8607: -- I see this same problem for other dynamic fields, not just the catch

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122721#comment-15122721 ] Anshum Gupta commented on SOLR-8619: Sure, I strongly think we need to be intelligent in electing

[jira] [Commented] (SOLR-8619) A new replica should not become leader when all current replicas are down as it leads to data loss

[ https://issues.apache.org/jira/browse/SOLR-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122781#comment-15122781 ] Jason Gerlowski commented on SOLR-8619: --- Throwing in my 2 cents. New to SolrCloud, so feel free to

[jira] [Updated] (SOLR-8529) Improve JdbcTest to not use plain assert statements

[ https://issues.apache.org/jira/browse/SOLR-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8529: --- Attachment: SOLR-8529.patch Updated to master. > Improve JdbcTest to not use plain assert statements

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121492#comment-15121492 ] Kevin Risden commented on SOLR-8602: For reference, on MySQL "select id, bad from test" results in an

[jira] [Resolved] (SOLR-8371) Try and prevent too many recovery requests from stacking up and clean up some faulty logic.

[ https://issues.apache.org/jira/browse/SOLR-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-8371. --- Resolution: Fixed Fix Version/s: Trunk 5.5 > Try and prevent too many

[jira] [Commented] (SOLR-8613) SolrJ JDBC - SQL queries with limit do not fail when a bad column is provided

[ https://issues.apache.org/jira/browse/SOLR-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121520#comment-15121520 ] Kevin Risden commented on SOLR-8613: See comments around here:

[jira] [Comment Edited] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121492#comment-15121492 ] Kevin Risden edited comment on SOLR-8602 at 1/28/16 2:08 PM: - For reference, on

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121468#comment-15121468 ] Kevin Risden commented on SOLR-8602: changed new RuntimeException(MESSAGE) to new

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121489#comment-15121489 ] Joel Bernstein commented on SOLR-8602: -- The code I was reviewing already was doing that in the

[jira] [Created] (SOLR-8613) SolrJ JDBC - SQL queries with limit do not fail when a bad column is provided

Kevin Risden created SOLR-8613: -- Summary: SolrJ JDBC - SQL queries with limit do not fail when a bad column is provided Key: SOLR-8613 URL: https://issues.apache.org/jira/browse/SOLR-8613 Project: Solr

Re: "newdev" Label Reminder

Thanks for the reminder Jason; I'll keep this in mind. I'll create an issue today I have in mind as appropriate for newdev :-) On Thu, Jan 28, 2016 at 8:56 AM Jason Gerlowski wrote: > Hi all, > > Just wanted to remind everyone of the "newdev" label, which is used to >

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121563#comment-15121563 ] Joel Bernstein commented on SOLR-8602: -- Ok, I'll review. > Implement ResultSetImpl.wasNull() >

[jira] [Commented] (SOLR-8602) Implement ResultSetImpl.wasNull()

[ https://issues.apache.org/jira/browse/SOLR-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121776#comment-15121776 ] Joel Bernstein commented on SOLR-8602: -- Planning on committing this shortly. > Implement

[jira] [Commented] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

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

[jira] [Commented] (SOLR-8616) Consider using multiple threads for publishCoresAsDown.

[ https://issues.apache.org/jira/browse/SOLR-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121810#comment-15121810 ] Mark Miller commented on SOLR-8616: --- Yeah, that would be nice. > Consider using multiple threads for

[jira] [Commented] (SOLR-3274) ZooKeeper related SolrCloud problems

[ https://issues.apache.org/jira/browse/SOLR-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121836#comment-15121836 ] Dan Kogan commented on SOLR-3274: - It appears we also ran into this issue using SolrCloud 5.4. This is the

[jira] [Comment Edited] (SOLR-3274) ZooKeeper related SolrCloud problems

[ https://issues.apache.org/jira/browse/SOLR-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121836#comment-15121836 ] Dan Kogan edited comment on SOLR-3274 at 1/28/16 4:30 PM: -- It appears we also ran

Re: lucene-solr git commit: fix false failures from test bugs

Hi Mike, My Jenkins's nightly monster trunk job failed on both these tests last night, and the seeds no longer reproduce after your fix. However, a third test failed in the same run, and it still reproduces for me - not sure if it’s related though: —— [junit4] Suite:

[jira] [Updated] (SOLR-8527) Improve JdbcTest to cleanup properly on failures

[ https://issues.apache.org/jira/browse/SOLR-8527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8527: --- Attachment: SOLR-8527.patch rebased on master. > Improve JdbcTest to cleanup properly on failures >

[jira] [Commented] (SOLR-7981) term based ValueSourceParsers should support an option to run an analyzer for hte specified field on the input

[ https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121631#comment-15121631 ] Shashank Tyagi commented on SOLR-7981: -- Thanks > term based ValueSourceParsers should support an

[jira] [Updated] (SOLR-8529) Improve JdbcTest to not use plain assert statements

[ https://issues.apache.org/jira/browse/SOLR-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8529: --- Attachment: SOLR-8529.patch Based on top of SOLR-8527 > Improve JdbcTest to not use plain assert

[jira] [Commented] (SOLR-7536) adding fields to newly created managed-schema could sometimes cause error

[ https://issues.apache.org/jira/browse/SOLR-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121649#comment-15121649 ] Steve Rowe commented on SOLR-7536: -- [~kiranch] had this problem with Solr 5.3.1 and showed me the logs.

[jira] [Commented] (SOLR-4722) Highlighter which generates a list of query term position(s) for each item in a list of documents, or returns null if highlighting is disabled.

[ https://issues.apache.org/jira/browse/SOLR-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121645#comment-15121645 ] Lee Wheless commented on SOLR-4722: --- Has anyone tried this in version 5.4.0? > Highlighter which

[jira] [Updated] (SOLR-8579) Replace old Solr logo on Lucene TLP website

[ https://issues.apache.org/jira/browse/SOLR-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-8579: -- Attachment: download-button.patch First attempt at changing color of Solr download button:

[jira] [Commented] (SOLR-8614) Add simple SolrClient.setUseXmlFormat

[ https://issues.apache.org/jira/browse/SOLR-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121658#comment-15121658 ] Yonik Seeley commented on SOLR-8614: When/why would we recommend that a user use XML instead of the

[jira] [Created] (LUCENE-7000) Split BasePointFormatTestCase from TestPointValues

Robert Muir created LUCENE-7000: --- Summary: Split BasePointFormatTestCase from TestPointValues Key: LUCENE-7000 URL: https://issues.apache.org/jira/browse/LUCENE-7000 Project: Lucene - Core

[jira] [Updated] (LUCENE-7000) Split BasePointFormatTestCase from TestPointValues

[ https://issues.apache.org/jira/browse/LUCENE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-7000: Attachment: LUCENE-7000.patch patch: there is some followup we can do (e.g. some of the tests are

<    1   2   3   >