Re: Creating single CloudSolrClient object which can be used throughout the application

Hello Shawn, I wasn't explicitly closing the client object but I fetched the client object inside the try block and this seems to automatically destroy the client object. Taking it out of the try block worked like magic. Problem solved! Best On Wed, Jul 4, 2018 at 10:40 PM Shawn Heisey

Re: AddReplica to shard with lowest node count

The rule based replica placement was deprecated. The autoscaling APIs are the way to go. Please see http://lucene.apache.org/solr/guide/7_3/solrcloud-autoscaling.html Your use-case is interesting. By default, the trigger for nodeAdded event will move replicas from the most loaded nodes to the new

Re: AddReplica to shard with lowest node count

Perhaps the rule based replica placement stuff would do the trick? https://lucene.apache.org/solr/guide/7_3/rule-based-replica-placement.html I haven't used it myself but I've seen lots of work going into it lately... On Wed, Jul 4, 2018 at 12:35 PM, Duncan, Adam wrote: > Hi all, > > Our team

Re: Solr - zoo with more than 1000 collections

Hi Bertrand, Are you by any chance using the new Time Routed Aliases feature? You didn't mention it so I suspect not, but you might want to look... It's still pretty new, but it would be interesting to get your feedback on it if it looks like it would help. I'm wondering how you get to that many

Re: Indexing part of Binary Documents and not the entire contents

You might consider using a free tool like JesterJ (www.jesterj.org) which can possibly also automate the acquisition of the documents and transmission to solr. As well as provide a framework for massaging the contents of the document in between (including Tika processing) (Disclaimer: I'm the

Re: MergeException due to illegal state in PerFieldPostingsFormat in 7.3.1

On 04.07.2018 19:01, Shawn Heisey wrote: > On 7/4/2018 1:36 AM, Benoit Delbosc wrote: >> I have a complex integration test that is failing systematically since >> we upgraded the Elasticsearch cluster to 6.3.0 (Lucene 7.3.1). > > This is a Solr mailing list.  Solr is a subproject of Lucene, but it

Re: [SECURITY] CVE-2018-8026: XXE vulnerability due to Apache Solr configset upload (exchange rate provider config / enum field config / TIKA parsecontext)

The cve id was reserved in April. The jira ticket 1 mo ago. Is this the first notice to this list? Thx On Wed, Jul 4, 2018, 12:56 PM Uwe Schindler wrote: > CVE-2018-8026: XXE vulnerability due to Apache Solr configset upload > (exchange rate provider config / enum field config / TIKA

Re: Parent-child query; subqueries on child docs of the same set of fields

agh... It's my pet peeve. what about q= {!parent which="isParent:true" v='attrname:genre AND attrvalue:drama'} AND {!parent which="isParent:true" v='attrname:country AND attrvalue:USA'} ^leading space q=_query_:{!parent which="isParent:true" v='attrname:genre AND attrvalue:drama'} AND

Re: Creating single CloudSolrClient object which can be used throughout the application

On 7/4/2018 2:41 AM, Ritesh Kumar wrote: I did exactly as you told, created a public static synchronized method. The problem still exists. I wasn't addressing the connection problem.  I was addressing the question in the subject -- one client object that you can use everywhere.  But I think

Re: MergeException due to illegal state in PerFieldPostingsFormat in 7.3.1

On 7/4/2018 1:36 AM, Benoit Delbosc wrote: I have a complex integration test that is failing systematically since we upgraded the Elasticsearch cluster to 6.3.0 (Lucene 7.3.1). This is a Solr mailing list.  Solr is a subproject of Lucene, but it is not Lucene. Solr and elasticsearch are

[SECURITY] CVE-2018-8026: XXE vulnerability due to Apache Solr configset upload (exchange rate provider config / enum field config / TIKA parsecontext)

CVE-2018-8026: XXE vulnerability due to Apache Solr configset upload (exchange rate provider config / enum field config / TIKA parsecontext) Severity: High Vendor: The Apache Software Foundation Versions Affected: Solr 6.0.0 to 6.6.4 Solr 7.0.0 to 7.3.1 Description: The details of this

AddReplica to shard with lowest node count

Hi all, Our team use Solrcloud for Solr 5.1 and are investigating an upgrade to 7.3 Currently we have a working scale-up approach for adding a new server to the cluster beyond the initial collection creation. We’ve automated the install of Solr on new servers and, following that, we register

Re: Block Join Child Query returns incorrect result

Mikhail Khludnev-2 wrote > Hello. > > {!parent} always searching for parents, some improvement is in progress, > but you need to use [child] or [subquery] to see children. > If you don't have an idea about search result add =true param to > get through matching details. > > On Mon, Jul 2, 2018

Re: push to the limit without going over

First, I usually prefer to construct your CloudSolrClient by using the Zookeeper ensemble string rather than URLs, although that's probably not a cure for your problem. Here's what I _think_ is happening. If you're slamming Solr with a lot of updates, you're doing a lot of merging. At some point

Re: Filtering solr suggest results

Hi Peter, Thanks for the help. Didn't see it before. Thanks, Arunan *Sugunakumar Arunan* Undergraduate - CSE | UOM On 3 July 2018 at 18:50, Peter Lancaster wrote: > Hi Arunan, > > You can use a context filter query as described https://lucene.apache.org/ > solr/guide/6_6/suggester.html > >

RE: 7.3 appears to leak

Hello Andrey, I didn't think of that! I will try it when i have the courage again, probably next week or so. Many thanks, Markus -Original message- > From:Kydryavtsev Andrey > Sent: Wednesday 4th July 2018 14:48 > To: solr-user@lucene.apache.org > Subject: Re: 7.3 appears to leak >

Re: 7.3 appears to leak

If it is not possible to find a resource leak by code analysis and there is no better ideas, I can suggest a brute force approach: - Clone Solr's sources from appropriate branch  https://github.com/apache/lucene-solr/tree/branch_7_3 - Log every searcher's holder increment/decrement operation in a

How to only highlight terms that caused the document to match

Hi list, I'm having difficulties getting the solr highlighter to highlight only the terms that actually caused the match. Let med explain: Given a query "john OR (peter AND mary)" and two documents: "john is awesome and so is peter" "peter is awesome and so is mary", solr will highlight "peter"

Re: Scores with Solr Suggester

Hi Christine, it depends on the suggester implementation, the one that got closer in having a score implementation is the BlendedInfix[1] but it is still in the TO DO phase. Feel free to contribute it if you like ! [1]

push to the limit without going over

Hi Solr Folk, I am trying to push solr to the limit and sometimes I succeed. The questions is how to not go over it, e.g., avoid: java.lang.RuntimeException: Tried fetching cluster state using the node names we knew of, i.e. [192.168.56.1:9998_solr, 192.168.56.1:9997_solr,

Re: Creating single CloudSolrClient object which can be used throughout the application

Hello Shawn, I did exactly as you told, created a public static synchronized method. The problem still exists. Maybe returning the client object if it is not null is causing " java.lang.IllegalStateException: Connection pool shut down" error. It does run fine for just one time. pseudo code:

MergeException due to illegal state in PerFieldPostingsFormat in 7.3.1

Greetings, I have a complex integration test that is failing systematically since we upgraded the Elasticsearch cluster to 6.3.0 (Lucene 7.3.1). The exact same test using an Elasticsearch cluster in version 6.2.4 (Lucene 7.2.1) is successful. Basically the test is submitting concurrent indexing

Re: Errors when using Blob API

Thanks shawn. I removed the space from header because I got another error. I finally used "Content-Type: application/octet-stream" instead of 'Content-Type: application/octet-stream' and all of errors even the space limit error solved. -- Sent from: