Re: Facet on same field in different ways

Thanks guys. The syntax "facet.field={!key=abc facet.limit=10}facetFieldName" works. On Tue, Jun 16, 2015 at 11:22 AM, Chris Hostetter wrote: > > : Have you tried this syntax ? > : > : &facet=true&facet.field={!ex=st key=terms facet.limit=5 > : facet.prefix=ap}query_terms&facet.field={!key=term

Facet on same field in different ways

Hi guys, Is there a way to facet on same field in *different ways?* For example, using a different facet.prefix. Here are the details facet.field={!key=myKey}myField&facet.prefix=p ==> works facet.field={!key=myKey}myField&f.myField.facet.prefix=p ==> works facet.field={!key=myKey}myFie

Re: facet name using {!key} doesn't work for interval facets

ure to get directions > relevant to your version. > > Upayavira > > On Fri, Jun 12, 2015, at 07:22 PM, Phanindra R wrote: > > Hi, > > > > According to > > > https://cwiki.apache.org/confluence/display/solr/Faceting#Faceting-IntervalFaceting > , > >

facet name using {!key} doesn't work for interval facets

Hi, According to https://cwiki.apache.org/confluence/display/solr/Faceting#Faceting-IntervalFaceting, a facet name could be assigned to interval facets, which then replaces the field name as the facet name in the response. The syntax I used: facet.interval={!key=myName}myField But Solr 4.10

Resource leak(?) when closing CloudSolrServer

Hi, Our indexing job and expiration job run every ~60 minutes (for about 10 minutes) in the test environment, within same JVM. Every job creates a new CloudSolrServer (decision was taken keeping other parts of system design in mind) and invokes shutdown() after it's complete. We have been seeing

Resource closing of CloudSolrServer

Hi, Our indexing job and expiration job run every ~60 minutes (for about 10 minutes) in the test environment, within same JVM. Every job creates a new CloudSolrServer (decision was taken keeping other parts of system design in mind) and invokes shutdown() after it's complete. We have been seeing

Re: Customizing Solr; Where to draw the line?

rt. > On Jun 8, 2014 10:38 PM, "Phanindra R" wrote: > > > Hi, > > > > We have decided to migrate from Lucene 3.x to latest Solr. A lot of > > architectural discussions are going on. There are two possible > approaches. > > > > Please note that

Customizing Solr; Where to draw the line?

Hi, We have decided to migrate from Lucene 3.x to latest Solr. A lot of architectural discussions are going on. There are two possible approaches. Please note that our customer-facing app (or any client) and Search are hosted on different machines. *1) Have a clean architecture* - Solr takes

Code that handles merging results from a distributed query

Hi, In Solr in Action book, I read how the distributed queries work. Looks like the node that receives the request executes a search, sends queries to other shards in parallel, and then finally merges the results. I've been trying to find where that piece of code exists. 1) Does the di