[JENKINS] Lucene-Artifacts-5.x - Build # 1074 - Failure

Build: https://builds.apache.org/job/Lucene-Artifacts-5.x/1074/ No tests ran. Build Log: [...truncated 7348 lines...] BUILD FAILED /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x/lucene/build.xml:427: The following error occurred while executing this line:

highlight on phrase search not working

Hi all, we're experiencing some problems in highlighting terms of a phrase search. I have already created a jira issue ( https://issues.apache.org/jira/browse/SOLR-8537) where the problem is explained in detail with minimal dataset to reproduce. Now I'm realizing that probably that wasn't the

[jira] [Updated] (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:all-tabpanel ] Christine Poerschke updated SOLR-8597: -- Attachment: SOLR-8597.patch Proposed patch against (git) master (formerly svn trunk). >

[jira] [Updated] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-5730: -- Attachment: SOLR-5730-part2of2.patch SOLR-5730-part1of2.patch > make

JIRA Notifications & Github PR Notifications

Hi all, You might have noticed that JIRA no longer automatically gets the usual commit comments! I contacted Daniel and he activated it, many thanks. With the next update of the Jenkins infrastructure (in a few hours), the "ASF Git and Subversion Bot" will also record pushes to JIRA. Daniel

[jira] [Commented] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117111#comment-15117111 ] Christine Poerschke commented on SOLR-5730: --- The revised attached patch uses this alternative. A

[jira] [Resolved] (LUCENE-6470) make all TermsQuery ctors efficient

[ https://issues.apache.org/jira/browse/LUCENE-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-6470. - Resolution: Fixed Fix Version/s: Trunk 5.5 > make all TermsQuery ctors

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

Christine Poerschke created SOLR-8597: - Summary: add default, no-op QParserPlugin.init(NamedList) method Key: SOLR-8597 URL: https://issues.apache.org/jira/browse/SOLR-8597 Project: Solr

Re: [JENKINS-EA] Lucene-Solr-5.x-Linux (32bit/jdk-9-ea+95) - Build # 15356 - Failure!

I'll try to figure this one out. I think all failures are with DFI... On Tue, Jan 26, 2016 at 3:45 AM, Policeman Jenkins Server wrote: > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15356/ > Java: 32bit/jdk-9-ea+95 -client -XX:+UseConcMarkSweepGC

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1665/ No tests ran. Build Log: [...truncated 24699 lines...] BUILD FAILED /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:756: The following error occurred while executing this line:

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/3039/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication Error Message:

Re: Merge vs Rebase

+1 for stealing the Hadoop guide wrt commit guidelines. I find their approach straight forward and I am a fan of attempting to keep a linear history, as we did in svn. - Dennis On Mon, Jan 25, 2016 at 7:50 PM, Erick Erickson wrote: > P.S. with attribution re: the

[jira] [Updated] (SOLR-8596) Web UI doesn't correctly generate queries which include local parameters

[ https://issues.apache.org/jira/browse/SOLR-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Teijeiro Flórez updated SOLR-8596: - Description: When configuring the "Raw Query Parameters" field for a query with a

[jira] [Commented] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117104#comment-15117104 ] Christine Poerschke commented on SOLR-5730: --- Have chosen {code} + if (segmentTerminatedEarly

Re: Merge vs Rebase

I don't think we should follow the hadoop dev practices, just look at the quality of the code they produce... On Mon, Jan 25, 2016 at 7:49 PM, Erick Erickson wrote: > OK, I'm _really tempted_ to just steal the Hadoop guide verbatim as a > start and we can refine as

[jira] [Created] (SOLR-8596) Web UI doesn't correctly generate queries which include local parameters

Ismael Teijeiro Flórez created SOLR-8596: Summary: Web UI doesn't correctly generate queries which include local parameters Key: SOLR-8596 URL: https://issues.apache.org/jira/browse/SOLR-8596

[jira] [Updated] (SOLR-8566) umbrella ticket: various initialCapacity tweaks (Fix Versions: trunk 5.5)

[ https://issues.apache.org/jira/browse/SOLR-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-8566: -- Attachment: SyncStrategy-syncWithReplicas.patch Trivial change. And so perfect to be my

[JENKINS] Lucene-Solr-5.x-Linux (32bit/jdk1.8.0_66) - Build # 15366 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15366/ Java: 32bit/jdk1.8.0_66 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication Error Message: Index: 0, Size: 0 Stack Trace:

Re: Ongoing index maintenance

Hi, I don't think the Lucene layer is lacking in this regard. Higher up the stack in Solr (or ES), it's conceivable one could do some of the functions you propose by adding by wrapping the reader (FilteredReader) that then does what you want -- removing a field, renaming a field, aliasing a

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 3941 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/3941/ 1 tests failed. FAILED: org.apache.solr.index.hdfs.CheckHdfsIndexTest.doTest Error Message: Could not find a healthy node to handle the request. Stack Trace: org.apache.solr.common.SolrException: Could not find a healthy

[jira] [Commented] (LUCENE-6956) TestBKDTree.testRandomMedium() failure: some hits were wrong

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

Fwd: Broken link in footer > Features > Data Handling link of lucene.apache.org/solr

FYI > Begin forwarded message: > > From: Kolby Heacock > Subject: Broken link in footer > Features > Data Handling link of > lucene.apache.org/solr > Date: January 26, 2016 at 4:11:57 PM PST > To: webmas...@apache.org > > Hello, > > I hope you are doing well today. >

[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=15118596#comment-15118596 ] Yonik Seeley commented on SOLR-8586: bq. I wonder if adding hashes of the version might be prone to

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1666/ No tests ran. Build Log: [...truncated 27313 lines...] BUILD FAILED /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-trunk/build.xml:756: The following error occurred while executing this line:

[jira] [Commented] (SOLR-8522) ImplicitSnitch to support IPv4 fragment and host name fragment tags

[ https://issues.apache.org/jira/browse/SOLR-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15118828#comment-15118828 ] Noble Paul commented on SOLR-8522: -- I don't think this is complete imagine I provide

[jira] [Commented] (LUCENE-6937) Migrate Lucene project from SVN to Git.

[ https://issues.apache.org/jira/browse/LUCENE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15118829#comment-15118829 ] Uwe Schindler commented on LUCENE-6937: --- Thanks Dawid! The discussions on the ML are just usual...

[jira] [Commented] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15118799#comment-15118799 ] Shai Erera commented on SOLR-5730: -- Rethinking my proposal, I'm not sure chaining merge policies is the

[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15658 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15658/ Java: 32bit/jdk-9-ea+95 -server -XX:+UseParallelGC -XX:-CompactStrings 2 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: Error from server at

[JENKINS-EA] Lucene-Solr-5.x-Linux (32bit/jdk-9-ea+95) - Build # 15356 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15356/ Java: 32bit/jdk-9-ea+95 -client -XX:+UseConcMarkSweepGC -XX:-CompactStrings 2 tests failed. FAILED: org.apache.lucene.queries.CommonTermsQueryTest.testMinShouldMatch Error Message: Stack Trace: java.lang.AssertionError

[jira] [Commented] (SOLR-8566) umbrella ticket: various initialCapacity tweaks (Fix Versions: trunk 5.5)

[ https://issues.apache.org/jira/browse/SOLR-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117196#comment-15117196 ] Christine Poerschke commented on SOLR-8566: --- First git commits for this ticket: * SOLR-8566:

[jira] [Commented] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117197#comment-15117197 ] Joel Bernstein commented on SOLR-8518: -- Before we commit to this approach I have a question. How much

[jira] [Updated] (SOLR-8566) umbrella ticket: various initialCapacity tweaks (Fix Versions: trunk/master 5.5)

[ https://issues.apache.org/jira/browse/SOLR-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-8566: -- Summary: umbrella ticket: various initialCapacity tweaks (Fix Versions: trunk/master

[jira] [Comment Edited] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117197#comment-15117197 ] Joel Bernstein edited comment on SOLR-8518 at 1/26/16 1:47 PM: --- Before we

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117213#comment-15117213 ] Robert Muir commented on LUCENE-6995: - this is a really good idea. otherwise we are going to get bug

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117214#comment-15117214 ] Dawid Weiss commented on LUCENE-6995: - This is interesting because I don't see this behavior. When I

Re: Merge vs Rebase

I am entirely serious, but we all know the code quality problems with hadoop. Many are the same ones Uwe has already fought here and you can already find issues/discussions on them: * any hadoop maven artifact is "jar hell in a box" * hadoop classes do crazy shit, like execute operating system

Classloaders, SPI, Directory ... OSGi?

Folks, Down at the bottom level of the SPI mechanism, the API accepts ClassLoader objects. However, the Directory API does not have methods that take a class loader, so, in practical terms, the SPI mechanism always uses the Thread Context Class Loader. I just spent some time sorting out a muddle

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117255#comment-15117255 ] Uwe Schindler commented on LUCENE-6995: --- I think the problem is also that when changing branches

[jira] [Comment Edited] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117255#comment-15117255 ] Uwe Schindler edited comment on LUCENE-6995 at 1/26/16 2:19 PM: I think

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117268#comment-15117268 ] Dawid Weiss commented on LUCENE-6995: - I think it's your build folders that are in an insane state,

RE: Classloaders, SPI, Directory ... OSGi?

Hi, > Down at the bottom level of the SPI mechanism, the API accepts > ClassLoader objects. However, the Directory API does not have methods > that take a class loader, so, in practical terms, the SPI mechanism > always uses the Thread Context Class Loader. Not entirely true. We use context

[jira] [Commented] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117294#comment-15117294 ] Kevin Risden commented on SOLR-8518: Well a very rough DBVisualizer is currently working as of

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

[ https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117295#comment-15117295 ] Steve Molloy commented on SOLR-8589: There's already a ticket about listing aliases. > Add aliases to

[jira] [Updated] (SOLR-8502) Improve Solr JDBC Driver to support SQL Clients like DBVisualizer

[ https://issues.apache.org/jira/browse/SOLR-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated SOLR-8502: --- Attachment: screenshot-1.png > Improve Solr JDBC Driver to support SQL Clients like DBVisualizer >

[jira] [Commented] (SOLR-8502) Improve Solr JDBC Driver to support SQL Clients like DBVisualizer

[ https://issues.apache.org/jira/browse/SOLR-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117303#comment-15117303 ] Kevin Risden commented on SOLR-8502: Added screenshot-1.png to show that rough DBVisualizer is working.

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117304#comment-15117304 ] Robert Muir commented on LUCENE-6995: - It happened to me twice this morning already. Just doing

[jira] [Commented] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117305#comment-15117305 ] Joel Bernstein commented on SOLR-8518: -- Ok, we'll go with the latest patch then. I think the main goal

[jira] [Commented] (SOLR-8502) Improve Solr JDBC Driver to support SQL Clients like DBVisualizer

[ https://issues.apache.org/jira/browse/SOLR-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117319#comment-15117319 ] Joel Bernstein commented on SOLR-8502: -- This looks great! > Improve Solr JDBC Driver to support SQL

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117322#comment-15117322 ] Dawid Weiss commented on LUCENE-6995: - Ok, but this isn't related to timestamps on version-controlled

[jira] [Created] (SOLR-8598) improve error handling in JSON Facet API

Yonik Seeley created SOLR-8598: -- Summary: improve error handling in JSON Facet API Key: SOLR-8598 URL: https://issues.apache.org/jira/browse/SOLR-8598 Project: Solr Issue Type: Improvement

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117331#comment-15117331 ] Erik Hatcher commented on LUCENE-6995: -- bq. ...have branch-dedicated build folder I like that idea!

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

[ https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117335#comment-15117335 ] Shawn Heisey commented on SOLR-8589: [~smolloy], either approach is viable. My approach does not

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117337#comment-15117337 ] Robert Muir commented on LUCENE-6995: - {quote} If so, it'd be an interesting exercise to not clean

[jira] [Updated] (SOLR-8598) improve error handling in JSON Facet API

[ https://issues.apache.org/jira/browse/SOLR-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-8598: --- Attachment: SOLR-8598.patch Here's a patch + test to improve the error message for an unknown

[jira] [Assigned] (SOLR-8598) improve error handling in JSON Facet API

[ https://issues.apache.org/jira/browse/SOLR-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley reassigned SOLR-8598: -- Assignee: Yonik Seeley > improve error handling in JSON Facet API >

[jira] [Updated] (SOLR-8598) improve error handling in JSON Facet API

[ https://issues.apache.org/jira/browse/SOLR-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-8598: --- Component/s: Facet Module > improve error handling in JSON Facet API >

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

[ https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117342#comment-15117342 ] Steve Molloy commented on SOLR-8589: Sure, just wanted to make sure they're linked. I'm already using

Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1074 - Failure

This is pretty strange - I looked on lucene1-us-west.apache.org, and the lucene/build/lucene.tgz.unpacked/ directory does not exist. The trunk version of this job has succeeded twice on ASF Jenkins. I just locally ran ‘ant prepare-release-no-sign’ on branch_5x under lucene/ and it built

[jira] [Updated] (SOLR-8590) example/files improvements

[ https://issues.apache.org/jira/browse/SOLR-8590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Hatcher updated SOLR-8590: --- Description: There are several example/files improvements/fixes that are warranted: * Fix e-mail and

[jira] [Comment Edited] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117337#comment-15117337 ] Robert Muir edited comment on LUCENE-6995 at 1/26/16 3:00 PM: -- {quote} If

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117354#comment-15117354 ] Uwe Schindler commented on LUCENE-6995: --- bq. I guess it will force us to fix places in the

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

[ https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117356#comment-15117356 ] Yago Riveiro commented on SOLR-8589: How is exposed aliases list in SOLR-4968? > Add aliases to the

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117355#comment-15117355 ] Dawid Weiss commented on LUCENE-6995: - Yes, absolutely. Ant clean should really clean everything. As

reviews.apache.org / GIT migration

Hello. Having not used it before, I'd like to try out reviews.apache.org (even though it's only been used a few times for the project in the past based on the https://reviews.apache.org/groups/lucene/ listing). The review board seems so far unware of the svn-to-git migration. Other projects

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/352/ Java: multiarch/jdk1.7.0 -d32 -client -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.security.TestAuthorizationFramework.authorizationFrameworkTest Error Message: KeeperErrorCode = Session expired for

[JENKINS] Lucene-Solr-NightlyTests-trunk - Build # 920 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/920/ 3 tests failed. FAILED: org.apache.solr.cloud.DistribDocExpirationUpdateProcessorTest.test Error Message: Exactly one shard should have changed, instead: [shard2, shard1] nodes=([core_node3(shard2), core_node2(shard1),

[jira] [Commented] (SOLR-8537) phrase highlighter doesn't work when searching for phrase containing some stopwords

[ https://issues.apache.org/jira/browse/SOLR-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117375#comment-15117375 ] David Smiley commented on SOLR-8537: Given that the 4.x series is EOL barring a critical bug (this

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

[ https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117379#comment-15117379 ] Shawn Heisey commented on SOLR-8589: bq. How is exposed aliases list in SOLR-4968? [~yriveiro], the

Re: Classloaders, SPI, Directory ... OSGi?

On Tue, Jan 26, 2016 at 9:35 AM, Uwe Schindler wrote: > Hi, > >> Down at the bottom level of the SPI mechanism, the API accepts >> ClassLoader objects. However, the Directory API does not have methods >> that take a class loader, so, in practical terms, the SPI mechanism >>

Re:reviews.apache.org / GIT migration

Looks like https://issues.apache.org/jira/browse/INFRA-7630 set up the original/existing review board. If there are no objections or existing ticket then I will raise a similar ticket towards the end of this week. Christine - Original Message - From: dev@lucene.apache.org To:

Re: highlight on phrase search not working

Hi Zaccheo, In general this developer community lives on JIRA. Since you have questions pertaining to that JIRA issue then simply put those comments there. I already commented on that issue a few minutes ago. The general info for "how to contribute" (to Solr; largely applies to Lucene too) is

[jira] [Commented] (LUCENE-6956) TestBKDTree.testRandomMedium() failure: some hits were wrong

[ https://issues.apache.org/jira/browse/LUCENE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117389#comment-15117389 ] Nicholas Knize commented on LUCENE-6956: ++ Thanks for reminding me where that came from! I

Re: reviews.apache.org / GIT migration

+1; I can't see how anyone would object to adding/retaining support for the tool. Nobody is forced to use it. I'm curious of the move to Git allows for possibly better options. I've heard good things about Gerrit but I've never tried it. I have mixed feelings of my experience with Reviewboard,

[jira] [Commented] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117421#comment-15117421 ] Joel Bernstein commented on SOLR-8518: -- I made a few slight changes and am running precommit now. 1)

Re: Merge vs Rebase

Rob, I'll trust your assessment of the technical deficiencies of the Hadoop codebase as I have no experience to say one way or the other. But I'm confused why this is relevant to wether they have a decent process & docs on how to use git? For reference I think Erick is referring to this:

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

[ https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117443#comment-15117443 ] Yago Riveiro commented on SOLR-8589: [~elyograg], as I said before, aliases are related with

Hmm Git mistake I believe

https://github.com/apache/lucene-solr/commit/bc815b5207638c676810699bae592fc8f3d93abd Is this something that I need to fix? These were my commands: defaultildsMBP5:lucene-solr joelbernstein$ git pull origin master remote: Counting objects: 507, done. remote: Compressing objects: 100% (66/66),

[jira] [Updated] (SOLR-8599) Errors in construction of SolrZooKeeper cause Solr to go into an inconsistent state

[ https://issues.apache.org/jira/browse/SOLR-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Laban updated SOLR-8599: -- Summary: Errors in construction of SolrZooKeeper cause Solr to go into an inconsistent state (was:

[jira] [Created] (SOLR-8599) Errors in construction of SolrZooKeeper cause Solr to into inconsistent state

Keith Laban created SOLR-8599: - Summary: Errors in construction of SolrZooKeeper cause Solr to into inconsistent state Key: SOLR-8599 URL: https://issues.apache.org/jira/browse/SOLR-8599 Project: Solr

[jira] [Commented] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117498#comment-15117498 ] Joel Bernstein commented on SOLR-8518: -- commit:

Re: Hmm Git mistake I believe

You can always use git pull --rebase, (make it the default) to not pollute the history with useless merge commits. This will fetch the changes from the server and rebase your commits on top of them (like svn does). On Tue, Jan 26, 2016 at 4:58 PM, Joel Bernstein wrote: > >

[jira] [Resolved] (SOLR-8518) Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName

[ https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein resolved SOLR-8518. -- Resolution: Implemented > Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName >

Re: Merge vs Rebase

On Tue, Jan 26, 2016 at 10:54 AM, david.w.smi...@gmail.com wrote: > My only critique of it is that I sense the git branch.autosetuprebase option > (what Yonik is using) might be obsoleted by the pull.rebase option; Maybe I don't understand what you're saying, but "git

Re: Merge vs Rebase

On Tue, Jan 26, 2016 at 10:54 AM, david.w.smi...@gmail.com wrote: > Rob, > I'll trust your assessment of the technical deficiencies of the Hadoop > codebase as I have no experience to say one way or the other. I will trust Rob's assessment too. > But I'm > confused why

[jira] [Created] (LUCENE-6996) Deconflict GeoPointField and BKD LatLonField Encoding, Decoding, and Tolerance

Nicholas Knize created LUCENE-6996: -- Summary: Deconflict GeoPointField and BKD LatLonField Encoding, Decoding, and Tolerance Key: LUCENE-6996 URL: https://issues.apache.org/jira/browse/LUCENE-6996

Re: Merge vs Rebase

On Tue, Jan 26, 2016 at 11:22 AM, Yonik Seeley wrote: > On Tue, Jan 26, 2016 at 10:54 AM, david.w.smi...@gmail.com > wrote: >> My only critique of it is that I sense the git branch.autosetuprebase option >> (what Yonik is using) might be obsoleted by

Re: Hmm Git mistake I believe

Why is this a problem? It records the fact that you had pull'd and had to merge your changes with what "came in" from master from other devs. Such historical accuracy, while looking "dirty" to some devs, is nevertheless accurate to what actually transpired, and can therefore be useful to future

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117531#comment-15117531 ] Michael McCandless commented on LUCENE-6995: +1 to close this trap ASAP. The errors you hit

Re: Hmm Git mistake I believe

Yep, it makes sense to me now. It's just a lot more information than I'm used to seeing with a commit. Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Jan 26, 2016 at 11:36 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > Why is this a problem? > > It records the fact that you

Re: Hmm Git mistake I believe

On Tue, Jan 26, 2016 at 11:36 AM, Michael McCandless wrote: > Why is this a problem? > > It records the fact that you had pull'd and had to merge your changes > with what "came in" from master from other devs. The branch just reflects when Joel last pulled changes

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117539#comment-15117539 ] Robert Muir commented on LUCENE-6995: - Can we iterate by committing this solution first, then working

[jira] [Created] (SOLR-8600) add & use ReRankQParserPlugin parameter [default] constants

Christine Poerschke created SOLR-8600: - Summary: add & use ReRankQParserPlugin parameter [default] constants Key: SOLR-8600 URL: https://issues.apache.org/jira/browse/SOLR-8600 Project: Solr

Re: Hmm Git mistake I believe

On Tue, Jan 26, 2016 at 11:37 AM Michael McCandless < luc...@mikemccandless.com> wrote: > and can therefore > be useful to future devs digging through the history. > > Some like to say that, but no one has given any concrete examples how this is useful to future devs. No duh someone that is

[jira] [Updated] (SOLR-8600) add & use ReRankQParserPlugin parameter [default] constants

[ https://issues.apache.org/jira/browse/SOLR-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-8600: -- Attachment: SOLR-8600.patch Proposed patch against master/trunk. > add & use

[jira] [Commented] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117549#comment-15117549 ] Shai Erera commented on SOLR-5730: -- I was hoping that we'd change solrconfig.xml to support something like

[jira] [Comment Edited] (SOLR-5730) make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector configurable in Solr

[ https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117549#comment-15117549 ] Shai Erera edited comment on SOLR-5730 at 1/26/16 4:51 PM: --- I was hoping that

[jira] [Commented] (LUCENE-6995) Add branch change trigger to common-build.xml to keep sane build on GIT branch change

[ https://issues.apache.org/jira/browse/LUCENE-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117550#comment-15117550 ] Uwe Schindler commented on LUCENE-6995: --- I have no problem committing and pushing this soon. I just

Re: Merge vs Rebase

They say the same thing about our horrid build system and so won't learn from our other good practices. What a stupid way to think on both sides. - Mark On Tue, Jan 26, 2016 at 11:30 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Tue, Jan 26, 2016 at 10:54 AM,

Re: Hmm Git mistake I believe

I understand it is "accurate" in the sense that it is more detailed as to what transpired -- at a cost of making the commit log more confusing should everyone do this. But I think this extra information is moot in simple cases like this -- i.e. "simple" in the sense that what he's working on

[jira] [Updated] (LUCENE-6956) TestBKDTree.testRandomMedium() failure: some hits were wrong

[ https://issues.apache.org/jira/browse/LUCENE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Knize updated LUCENE-6956: --- Attachment: LUCENE-6956.patch Updated patch that reverts BKD tolerance back to {{1e-7}}. I

  1   2   >