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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19888/ Java: 32bit/jdk1.8.0_131 -server -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.test Error Message: shard2 is not consistent. Got 1228 from

[jira] [Updated] (SOLR-9241) Rebalance API for SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Sharma updated SOLR-9241: --- Description: This is the v1 of the patch for Solrcloud Rebalance api (as described in

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/3768/ Java: 64bit/jdk1.8.0_131 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testCollectionsAPI Error Message: expected:<3> but was:<1> Stack Trace:

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-MacOSX/940/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 7 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test Error Message: Could not find collection:collection2 Stack Trace:

[jira] [Resolved] (LUCENE-7719) UnifiedHighlighter doesn't handle some AutomatonQuery's with multi-byte chars

[ https://issues.apache.org/jira/browse/LUCENE-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley resolved LUCENE-7719. -- Resolution: Fixed Fix Version/s: master (7.0) > UnifiedHighlighter doesn't handle some

[jira] [Commented] (LUCENE-7719) UnifiedHighlighter doesn't handle some AutomatonQuery's with multi-byte chars

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

[jira] [Commented] (LUCENE-7719) UnifiedHighlighter doesn't handle some AutomatonQuery's with multi-byte chars

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

[jira] [Updated] (SOLR-10864) Add static (test only) boolean to PointField indicating 'precisionStep' should be ignored

[ https://issues.apache.org/jira/browse/SOLR-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-10864: Attachment: SOLR-10864.patch Before diving in completely, here's a starting point patch for discussion to

[jira] [Updated] (SOLR-10503) CurrencyField should be changed from TrieLongField to LongPointField for underlying raw-polyfield

[ https://issues.apache.org/jira/browse/SOLR-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-10503: -- Attachment: SOLR-10503.patch Patch folding in [~hossman]'s feedback, and fixing SOLR-10502. >

[jira] [Commented] (LUCENE-7880) Make boolean query clause limit configurable per-query

[ https://issues.apache.org/jira/browse/LUCENE-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052625#comment-16052625 ] David Smiley commented on LUCENE-7880: -- +1 fine idea. With this new proposed option,

[jira] [Commented] (SOLR-10317) Solr Nightly Benchmarks

[ https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052624#comment-16052624 ] Vivek Narang commented on SOLR-10317: - Hi [~michael.sun]. Like you, I was also deeply concerned about

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052529#comment-16052529 ] Erick Erickson commented on SOLR-4586: -- Making it per-core would go a long way to making it easier to

[JENKINS] Lucene-Solr-master-Windows (32bit/jdk1.8.0_131) - Build # 6654 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6654/ Java: 32bit/jdk1.8.0_131 -server -XX:+UseConcMarkSweepGC 2 tests failed. FAILED: org.apache.solr.core.TestJmxIntegration.testJmxRegistration Error Message: org.apache.lucene.store.AlreadyClosedException: Already closed

[JENKINS-EA] Lucene-Solr-master-Linux (32bit/jdk-9-ea+173) - Build # 19886 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19886/ Java: 32bit/jdk-9-ea+173 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.update.HardAutoCommitTest.testCommitWithin Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052496#comment-16052496 ] Yonik Seeley commented on SOLR-4586: I opened LUCENE-7880 to try and at least remove the static-ness of

[jira] [Created] (LUCENE-7880) Make boolean query clause limit configurable per-query

Yonik Seeley created LUCENE-7880: Summary: Make boolean query clause limit configurable per-query Key: LUCENE-7880 URL: https://issues.apache.org/jira/browse/LUCENE-7880 Project: Lucene - Core

[jira] [Commented] (LUCENE-7868) Use multiple threads to apply deletes and DV updates

[ https://issues.apache.org/jira/browse/LUCENE-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052429#comment-16052429 ] Michael McCandless commented on LUCENE-7868: Thanks [~simonw]! I'll update the patch with

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052428#comment-16052428 ] Robert Muir commented on SOLR-4586: --- Sorry, I'm still -1 to that MAX_INT default. That hasn't changed.

[jira] [Updated] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-4586: -- Fix Version/s: (was: 6.0) (was: 5.2) master (7.0) >

[jira] [Updated] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-4586: -- Component/s: search > Eliminate the maxBooleanClauses limit > - > >

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052414#comment-16052414 ] Jan Høydahl commented on SOLR-4586: --- Cool. Keep it simple. Get rid of the thing in 7.0 (that would

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052377#comment-16052377 ] Yonik Seeley commented on SOLR-4586: +1 to remove this completely from all solrconfigs and set default

[jira] [Comment Edited] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052377#comment-16052377 ] Yonik Seeley edited comment on SOLR-4586 at 6/16/17 8:51 PM: - bq. +1 to remove

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052352#comment-16052352 ] Andrzej Bialecki commented on SOLR-4586: - .bq ...although stand-alone .vs. SolrCloud makes

[jira] [Commented] (LUCENE-7868) Use multiple threads to apply deletes and DV updates

[ https://issues.apache.org/jira/browse/LUCENE-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052351#comment-16052351 ] Simon Willnauer commented on LUCENE-7868: - [~mikemccand] i did a first pass at the patch... good

Re: Review Request 60154: LUCENE-7868: Concurrent deletes and doc values updates

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60154/#review178121 ---

[jira] [Commented] (SOLR-10880) Support replica filtering by flavour

[ https://issues.apache.org/jira/browse/SOLR-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052346#comment-16052346 ] Jan Høydahl commented on SOLR-10880: What about a generic tagging possibility - {{replica.tag}} which

[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression (and perhaps others) incorrectly handles fq clauses

[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052336#comment-16052336 ] Erick Erickson commented on SOLR-10908: --- Assigning to myself to track, but anyone else who wants to

[jira] [Assigned] (SOLR-10908) CloudSolrStream.toExpression (and perhaps others) incorrectly handles fq clauses

[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson reassigned SOLR-10908: - Assignee: Erick Erickson > CloudSolrStream.toExpression (and perhaps others) incorrectly

Re: /v2 API -- will there ever be a /v3?

My concern with /api is that handling backcompats between versions (v2 to v3 etc.) is problematic; and if we decide not to support backcompat, then it could be a source of confusion for the user. I'm +1 for /v2 or /api/v2 (and v3 etc. going forward). On Fri, Jun 16, 2017 at 10:53 PM, David

Re: /v2 API -- will there ever be a /v3?

+1 to remove the "v2" in the URL or make it an optional add-on (e.g. /api or /api/v2). Any/all of the proposals by Jan & Shawn sound reasonable to me. On Fri, Jun 16, 2017 at 9:59 AM Jan Høydahl wrote: > Hi, > > Now that we’re getting used to thinking localhost:8983/v2/

[jira] [Commented] (SOLR-5405) Cloud graph view not usable by color-blind users - request small tweak

[ https://issues.apache.org/jira/browse/SOLR-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052297#comment-16052297 ] Mark Miller commented on SOLR-5405: --- I've experienced the same thing. On a larger cluster it makes it

[jira] [Commented] (SOLR-10503) CurrencyField should be changed from TrieLongField to LongPointField for underlying raw-polyfield

[ https://issues.apache.org/jira/browse/SOLR-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052278#comment-16052278 ] Steve Rowe commented on SOLR-10503: --- Thanks for the review, [~hossman]. In general, I assumed that

[jira] [Created] (SOLR-10908) CloudSolrStream.toExpression (and perhaps others) incorrectly handles fq clauses

Erick Erickson created SOLR-10908: - Summary: CloudSolrStream.toExpression (and perhaps others) incorrectly handles fq clauses Key: SOLR-10908 URL: https://issues.apache.org/jira/browse/SOLR-10908

[jira] [Commented] (SOLR-10503) CurrencyField should be changed from TrieLongField to LongPointField for underlying raw-polyfield

[ https://issues.apache.org/jira/browse/SOLR-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052220#comment-16052220 ] Hoss Man commented on SOLR-10503: - * why copy so much of AbstractCurrencyFieldTest into a new

[jira] [Commented] (SOLR-10907) fix Resource Leak warning in ExpandComponent

[ https://issues.apache.org/jira/browse/SOLR-10907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052216#comment-16052216 ] Erick Erickson commented on SOLR-10907: --- Yep, sure does seem simple. But that's the exact pattern

[jira] [Commented] (SOLR-5405) Cloud graph view not usable by color-blind users - request small tweak

[ https://issues.apache.org/jira/browse/SOLR-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052208#comment-16052208 ] Erick Erickson commented on SOLR-5405: -- Christine: Well, I think it'd be a great t-shirt if we

Re: /v2 API -- will there ever be a /v3?

On 6/16/2017 7:59 AM, Jan Høydahl wrote: > Now that we’re getting used to thinking localhost:8983/v2/ as the new api > entry point, just one silly question: > > Will we ever move beyond /v2/ to /v3/? TL;DR: You sure you want to open this can of worms? This is one of my primary fears with

[jira] [Commented] (SOLR-10880) Support replica filtering by flavour

[ https://issues.apache.org/jira/browse/SOLR-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052163#comment-16052163 ] Christine Poerschke commented on SOLR-10880: (Disclosure: Domenico and I are in the same team

[jira] [Commented] (LUCENE-7848) QueryBuilder.analyzeGraphPhrase does not handle gaps correctly

[ https://issues.apache.org/jira/browse/LUCENE-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052152#comment-16052152 ] Dawid Weiss commented on LUCENE-7848: - On short holidays, Jim, but I'll try to review next week.

[jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit

[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052121#comment-16052121 ] Erick Erickson commented on SOLR-4586: -- +1 to moving it to solr.xml and/or clusterprop (although

(how) do folks use the Cloud Graph (Radial) in the Solr Admin UI?

Any thoughts on potentially removing the radial cloud graph? https://issues.apache.org/jira/browse/SOLR-5405 is the background for the question and further input and views would be very welcome. Thanks, Christine - To

[jira] [Commented] (SOLR-5405) Cloud graph view not usable by color-blind users - request small tweak

[ https://issues.apache.org/jira/browse/SOLR-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052117#comment-16052117 ] Christine Poerschke commented on SOLR-5405: --- Potentially controversial idea, could we *remove the

[jira] [Commented] (LUCENE-7872) TopDocs.totalHits should be a long

[ https://issues.apache.org/jira/browse/LUCENE-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052115#comment-16052115 ] Hoss Man commented on LUCENE-7872: -- bq. Doesn't DocList only represent results from a single shard?

[jira] [Commented] (SOLR-6671) Introduce a solr.data.home as root dir for all data

[ https://issues.apache.org/jira/browse/SOLR-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052109#comment-16052109 ] Jan Høydahl commented on SOLR-6671: --- Thanks Mark > Introduce a solr.data.home as root dir for all data >

[jira] [Updated] (SOLR-9623) Disable remote streaming by default

[ https://issues.apache.org/jira/browse/SOLR-9623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-9623: -- Attachment: SOLR-9623.patch New patch * Sets defaults for both multipartUploadLimitInKB and

[jira] [Updated] (SOLR-10907) fix Resource Leak warning in ExpandComponent

[ https://issues.apache.org/jira/browse/SOLR-10907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-10907: --- Attachment: SOLR-10907.patch Attaching proposed (this seems too easy-and-obvious?)

[jira] [Created] (SOLR-10907) fix Resource Leak warning in ExpandComponent

Christine Poerschke created SOLR-10907: -- Summary: fix Resource Leak warning in ExpandComponent Key: SOLR-10907 URL: https://issues.apache.org/jira/browse/SOLR-10907 Project: Solr Issue

[jira] [Assigned] (SOLR-10889) Stale zookeper information is used during failover check

[ https://issues.apache.org/jira/browse/SOLR-10889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller reassigned SOLR-10889: -- Assignee: Mark Miller > Stale zookeper information is used during failover check >

[jira] [Assigned] (SOLR-10904) Unnecessary waiting during failover in case of failed core creation

[ https://issues.apache.org/jira/browse/SOLR-10904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller reassigned SOLR-10904: -- Assignee: Mark Miller > Unnecessary waiting during failover in case of failed core creation >

[jira] [Assigned] (SOLR-10796) TestPointsField: increase randomized testing of non-trivial values

[ https://issues.apache.org/jira/browse/SOLR-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe reassigned SOLR-10796: - Assignee: Steve Rowe > TestPointsField: increase randomized testing of non-trivial values >

[jira] [Commented] (SOLR-9824) Documents indexed in bulk are replicated using too many HTTP requests

[ https://issues.apache.org/jira/browse/SOLR-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052059#comment-16052059 ] Mark Miller commented on SOLR-9824: --- Yeah, it's meant to go to 6.x. It was baking on 7. Tomas has likely

[jira] [Commented] (SOLR-6671) Introduce a solr.data.home as root dir for all data

[ https://issues.apache.org/jira/browse/SOLR-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052053#comment-16052053 ] Mark Miller commented on SOLR-6671: --- I've only read through the changes, but looks okay to me. >

[jira] [Commented] (SOLR-10338) Configure SecureRandom non blocking for tests.

[ https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052038#comment-16052038 ] Mark Miller commented on SOLR-10338: It tested out well for me as well, just got stuck in some other

[jira] [Commented] (SOLR-9989) Add support for PointFields in FacetModule (JSON Facets)

[ https://issues.apache.org/jira/browse/SOLR-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052035#comment-16052035 ] Yonik Seeley commented on SOLR-9989: Thanks, looking now... > Add support for PointFields in

[jira] [Reopened] (SOLR-9910) Allow setting of additional jetty options in bin/solr and bin/solr.cmd

[ https://issues.apache.org/jira/browse/SOLR-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller reopened SOLR-9910: --- > Allow setting of additional jetty options in bin/solr and bin/solr.cmd >

[jira] [Commented] (SOLR-9910) Allow setting of additional jetty options in bin/solr and bin/solr.cmd

[ https://issues.apache.org/jira/browse/SOLR-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052032#comment-16052032 ] Mark Miller commented on SOLR-9910: --- Because we had a vote and now publish that Jetty is an

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

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

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052028#comment-16052028 ] Noble Paul commented on SOLR-9565: -- fixed > Make every UpdateRequestProcessor available implicitly >

[jira] [Updated] (SOLR-9989) Add support for PointFields in FacetModule (JSON Facets)

[ https://issues.apache.org/jira/browse/SOLR-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-9989: --- Attachment: SOLR-9989.patch Rough patch for this ticket, [~ysee...@gmail.com] can you take a look? >

[jira] [Resolved] (LUCENE-7874) DisjunctionMaxQuery could rewrite to BooleanQuery when tiebreaker == 1

[ https://issues.apache.org/jira/browse/LUCENE-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ferenczi resolved LUCENE-7874. -- Resolution: Fixed Thanks [~jpountz] > DisjunctionMaxQuery could rewrite to BooleanQuery when

[jira] [Commented] (LUCENE-7874) DisjunctionMaxQuery could rewrite to BooleanQuery when tiebreaker == 1

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

[jira] [Commented] (SOLR-9623) Disable remote streaming by default

[ https://issues.apache.org/jira/browse/SOLR-9623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051999#comment-16051999 ] Yonik Seeley commented on SOLR-9623: Sorry, this fell off my radar. bq. [~yonik] any thought about

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051979#comment-16051979 ] Steve Rowe commented on SOLR-9565: -- In fact UpdateRequestProcessorFactoryTest.testRequestTimeUrp() fails

[JENKINS-EA] Lucene-Solr-master-Windows (64bit/jdk-9-ea+173) - Build # 6653 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6653/ Java: 64bit/jdk-9-ea+173 -XX:+UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: org.apache.solr.update.processor.UpdateRequestProcessorFactoryTest.testRequestTimeUrp Error Message: No such processor Template Stack

[jira] [Commented] (SOLR-9177) Support oom hook when running Solr in foreground mode

[ https://issues.apache.org/jira/browse/SOLR-9177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051976#comment-16051976 ] Shawn Heisey commented on SOLR-9177: bq. Are there benefits from running in foreground with systemd

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051975#comment-16051975 ] Steve Rowe commented on SOLR-9565: -- Policeman Jenkins found a reproducing master seed for a failure that

[jira] [Updated] (LUCENE-7874) DisjunctionMaxQuery could rewrite to BooleanQuery when tiebreaker == 1

[ https://issues.apache.org/jira/browse/LUCENE-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ferenczi updated LUCENE-7874: - Fix Version/s: master (7.0) > DisjunctionMaxQuery could rewrite to BooleanQuery when tiebreaker

[jira] [Updated] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

[ https://issues.apache.org/jira/browse/LUCENE-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ferenczi updated LUCENE-7878: - Affects Version/s: (was: 6.6.1) 6.5.1 Fix Version/s: 6.6.1 >

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

Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1868/ 2 tests failed. FAILED: org.apache.solr.update.AutoCommitTest.testMaxDocs Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception during query at

[jira] [Resolved] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

[ https://issues.apache.org/jira/browse/LUCENE-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ferenczi resolved LUCENE-7878. -- Resolution: Fixed Thanks @jpountz and Emmanuel for finding this nasty bug! It is merged in

[jira] [Updated] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

[ https://issues.apache.org/jira/browse/LUCENE-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ferenczi updated LUCENE-7878: - Affects Version/s: (was: 6.5.1) 6.6.1 > QueryParser AND default

[jira] [Commented] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

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

Re: Reference guide editing: newbie notes and kudos to Cassandra and Hoss:

You can make an all-in-one HTML if you make an .adoc page that uses "include" macros to pull in all the pages you want in the all-in-one HTML page. This is exactly how the PDF is generated, and one of the steps of the build process builds a data file that has all the pages in the proper hierarchy.

[jira] [Commented] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

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

/v2 API -- will there ever be a /v3?

Hi, Now that we’re getting used to thinking localhost:8983/v2/ as the new api entry point, just one silly question: Will we ever move beyond /v2/ to /v3/? The answer may seem obvious to many of you and may have consensus in some looong JIRA discussion that I did not follow. But I have a

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19882/ Java: 64bit/jdk1.8.0_131 -XX:-UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.update.processor.UpdateRequestProcessorFactoryTest.testRequestTimeUrp Error Message: No such processor Template Stack

[jira] [Commented] (LUCENE-7868) Use multiple threads to apply deletes and DV updates

[ https://issues.apache.org/jira/browse/LUCENE-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051880#comment-16051880 ] Michael McCandless commented on LUCENE-7868: I posted the last patch in Review Board:

Review Request 60154: LUCENE-7868: Concurrent deletes and doc values updates

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60154/ --- Review request for lucene. Repository: lucene-solr Description ---

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051855#comment-16051855 ] Jan Høydahl commented on SOLR-9565: --- My point is that adding something new like implicit URP, we should

[jira] [Comment Edited] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051827#comment-16051827 ] Noble Paul edited comment on SOLR-9565 at 6/16/17 12:56 PM: If you are

[jira] [Commented] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

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

[JENKINS] Lucene-Solr-NightlyTests-master - Build # 1327 - Still unstable

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1327/ 4 tests failed. FAILED: org.apache.solr.handler.extraction.TestExtractionDateUtil.testParseDate Error Message: Incorrect parsed timestamp: 1226583351000 != 1226579751000 (Thu Nov 13 04:35:51 AKST 2008) Stack Trace:

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051827#comment-16051827 ] Noble Paul commented on SOLR-9565: -- If you are suggesting that there should be a new and better way for

[jira] [Updated] (LUCENE-7878) QueryParser AND default operator and MultiWords synonyms failed if keywords exactly matches a synonym

[ https://issues.apache.org/jira/browse/LUCENE-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Ferenczi updated LUCENE-7878: - Fix Version/s: 6.7 master (7.0) > QueryParser AND default operator and

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1372/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.update.processor.UpdateRequestProcessorFactoryTest.testRequestTimeUrp Error Message: No such processor Template Stack

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051806#comment-16051806 ] Jan Høydahl commented on SOLR-9565: --- bq. What do you mean by hard coding? Nothing is hard coded See code

[jira] [Commented] (SOLR-6174) Facet count incorrect when duplicate facet queries (facet.query) are specified

[ https://issues.apache.org/jira/browse/SOLR-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051798#comment-16051798 ] Alessandro Benedetti commented on SOLR-6174: Hi [~hossman], I think that a combination of

[jira] [Commented] (SOLR-10906) Linux install script support for setting solr.solr.home, solr.data.home, solr.logs.dir mm

[ https://issues.apache.org/jira/browse/SOLR-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051773#comment-16051773 ] Jan Høydahl commented on SOLR-10906: Also it would be useful to be able to pass {{-z }}, {{-h }} and

[jira] [Commented] (SOLR-10903) Default configuration should use edismax for searching on all fields

[ https://issues.apache.org/jira/browse/SOLR-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051758#comment-16051758 ] Jan Høydahl commented on SOLR-10903: Quoting [my suggestion from

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19881/ Java: 64bit/jdk1.8.0_131 -XX:-UseCompressedOops -XX:+UseParallelGC 2 tests failed. FAILED: org.apache.solr.cloud.LeaderFailoverAfterPartitionTest.test Error Message: Expected 2 of 3 replicas to be active but only found 1;

JDK 9 EA Build 174 & JDK 8u152 b04 are available on jdk.java.net

Hi Uwe & Dawid, *JDK 9 Early Access* build 174 is available at : - jdk.java.net/9/ A summary of all the changes in this build are listed here . Changes which were introduced since the last availability email that may be of

[jira] [Comment Edited] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051706#comment-16051706 ] Noble Paul edited comment on SOLR-9565 at 6/16/17 9:58 AM: --- BTW, are you aware of

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051706#comment-16051706 ] Noble Paul commented on SOLR-9565: -- BTW, are you aware of the fact that names of {{qparserPlugin}},

[jira] [Comment Edited] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051688#comment-16051688 ] Noble Paul edited comment on SOLR-9565 at 6/16/17 9:48 AM: --- What do you mean by

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051688#comment-16051688 ] Noble Paul commented on SOLR-9565: -- What do you mean by hard coding? Nothing is hard coded. You can

[jira] [Commented] (LUCENE-7874) DisjunctionMaxQuery could rewrite to BooleanQuery when tiebreaker == 1

[ https://issues.apache.org/jira/browse/LUCENE-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051686#comment-16051686 ] Adrien Grand commented on LUCENE-7874: -- +1 > DisjunctionMaxQuery could rewrite to BooleanQuery when

[jira] [Commented] (LUCENE-7877) Replace PrefixAwareTokenStream

[ https://issues.apache.org/jira/browse/LUCENE-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051684#comment-16051684 ] Adrien Grand commented on LUCENE-7877: -- It looks good to me but I'm not as familiar with the

[jira] [Commented] (SOLR-9565) Make every UpdateRequestProcessor available implicitly

[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051671#comment-16051671 ] Jan Høydahl commented on SOLR-9565: --- bq. -1 on hard-coding certain plugins this way. it is an anti

[jira] [Commented] (SOLR-6671) Introduce a solr.data.home as root dir for all data

[ https://issues.apache.org/jira/browse/SOLR-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051661#comment-16051661 ] Jan Høydahl commented on SOLR-6671: --- Getting ready to commit this, hoping to target 7.0. Would really

  1   2   >