questions about default operator within solr query string
Hi, Nice to have a chance to discuss with solr experts! We are using solr as our search solution. But now we have a requirement that we don't know how to handle, even after we have looked through the Solr documentation. The solr version we used is 4.10.1. For the question, please refer to the following example url: http://10.90.44.33/solr/searcher/select?start=0&rows=24&fl=id,headline,slug&q=slug:variety-entertainment%20headline:entertainment&sort=score%20asc&debug=true With our default operator(q.op) is configured as "OR", the parsed query is: slug:variety slug:entertainment headline:entertainment But what we really want is as follows: +slug:variety+slug:entertainment headline:entertainment So, the question is: When searching , is there any way to configure the applied operator between the terms from the field "slug" to be "AND" and the operator between the fields "slug" and "headline" is "OR"? If no, could you please advise on how to handle this requirement in other ways? Thanks in advance Chun
Re: questions about default operator within solr query string
Hi Chun, Something like: +slug:variety +slug:entertainment headline:entertainment should work. But you may also want to use function queries for slug filtering: http://search-lucene.com/?q=fq&fc_project=Solr https://cwiki.apache.org/confluence/display/solr/Common+Query+Parameters#CommonQueryParameters-Thefq(FilterQuery)Parameter Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ On Mon, Jan 5, 2015 at 6:11 AM, wrote: > Hi, > > Nice to have a chance to discuss with solr experts! > > We are using solr as our search solution. But now we have a > requirement that we don't know how to handle, even after we have looked > through the Solr documentation. > > The solr version we used is 4.10.1. > > For the question, please refer to the following example url: > > > http://10.90.44.33/solr/searcher/select?start=0&rows=24&fl=id,headline,slug&q=slug:variety-entertainment%20headline:entertainment&sort=score%20asc&debug=true > > > With our default operator(q.op) is configured as "OR", the parsed > query is: > >slug:variety slug:entertainment headline:entertainment > > > But what we really want is as follows: > > +slug:variety+slug:entertainment headline:entertainment > > > So, the question is: > > When searching , is there any way to configure the applied > operator between the terms from the field "slug" to be "AND" and the > operator between the fields "slug" and "headline" is "OR"? > > If no, could you please advise on how to handle this > requirement in other ways? > > > Thanks in advance > > > Chun >
Re: questions about default operator within solr query string
You may want to put the slug portion of the query in filter queries (fq). Do you rank on slug or only use them for filtering? Asked another way, are some slugs more important than others or do you want them all to score the same? It would look like this: &fl=id,headline,slug&fq=slug:variety&fq=slug:entertainment&q=headline:entertainment Do you really want "&sort=score%20asc”? That shows the least relevant items (lowest score) first. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ On Jan 5, 2015, at 3:30 AM, Otis Gospodnetic wrote: > Hi Chun, > > Something like: > +slug:variety +slug:entertainment headline:entertainment should work. > > But you may also want to use function queries for slug filtering: > http://search-lucene.com/?q=fq&fc_project=Solr > https://cwiki.apache.org/confluence/display/solr/Common+Query+Parameters#CommonQueryParameters-Thefq(FilterQuery)Parameter > > Otis > -- > Monitoring * Alerting * Anomaly Detection * Centralized Log Management > Solr & Elasticsearch Support * http://sematext.com/ > > > On Mon, Jan 5, 2015 at 6:11 AM, wrote: > >> Hi, >> >> Nice to have a chance to discuss with solr experts! >> >> We are using solr as our search solution. But now we have a >> requirement that we don't know how to handle, even after we have looked >> through the Solr documentation. >> >> The solr version we used is 4.10.1. >> >> For the question, please refer to the following example url: >> >> >> http://10.90.44.33/solr/searcher/select?start=0&rows=24&fl=id,headline,slug&q=slug:variety-entertainment%20headline:entertainment&sort=score%20asc&debug=true >> >> >> With our default operator(q.op) is configured as "OR", the parsed >> query is: >> >> slug:variety slug:entertainment headline:entertainment >> >> >> But what we really want is as follows: >> >> +slug:variety+slug:entertainment headline:entertainment >> >> >> So, the question is: >> >> When searching , is there any way to configure the applied >> operator between the terms from the field "slug" to be "AND" and the >> operator between the fields "slug" and "headline" is "OR"? >> >> If no, could you please advise on how to handle this >> requirement in other ways? >> >> >> Thanks in advance >> >> >> Chun >>
Running Multiple Solr Instances
Hi folks, I am running multiple solr instances (Solr 4.10.3 on tomcat 8).There are 3 physical machines and I have 4 solr instances running on each machine on ports 8080,8081,8082 and 8083.The set up is well up to this point.Now I want to point each of these instance to a different index directories.The drives in the machines are mounted as d/1,d/2,d/3 ,d/4 etc.Now if I define /d/1 as the solr home all solr index directories are created in /d/1 where as the other drives remain un used.So how do I configure solr to make use of all the drives so that I can get maximum storage for solr.I would really appreciate any help in this regard. Thanks, Nishanth
How to limit the number of result sets of the 'export' handler
Using rows=xxx doesn't seem to work. Is there a way to do this?
Re: SolrCloud multi-datacenter failover?
Hi, Check http://search-lucene.com/?q=%22Cross+Data+Center+Replicaton%22 -> http://issues.apache.org/jira/browse/SOLR-6273 Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ On Fri, Jan 2, 2015 at 4:52 PM, jaime spicciati wrote: > All, > > At my current customer we have developed a custom federator that will > federate queries between Endeca and Solr to ease the transition from an > extremely large (TBs of data) Endeca index to Solr. (Endeca is similar to > Solr in terms of search/faceted navigation/etc). > > > > During this transition plan we need to support multi datacenter failover > which we have historically handled via load balancers with the appropriate > failover configurations (think F5). We are currently playing our dataloads > into multiple datacenters to ensure data consistency. (Each datacenter has > a stand-alone instance of solrcloud with its own redundancy/failover) > > > > I am curious to see how the community handles multi datacenter failureover > at the presentation layer (datacenter A goes down and we want to failover > to B). Solrcloud within a datacenter will handle single datacenter failure > within the instance, but in order to support multi datacenter failover I > haven't seen a definitive ‘answer’ as to how to handle this situation. > > > > At this point the only two options I can come up with are > > 1) Fail the entire datacenter if Solrcloud goes offline (GUI/index/etc go > offline) > > - This is problematic because some portion of user activity will fail, > queries that are in transit will not complete > > 2) Implement failover at the custom federator level. In doing so we would > need to detect a failure at datacenter A within our federator, then query > datacenter B to fulfill the user request, then potentially fail the entire > datacenter A once all transactions have been fulfilled against A > > > > Since we are looking up the active solr instance via zookeeper (solrcloud) > per datacenter I don’t see any reasonable means of failing over to another > datacenter if a given solrcloud instance goes down? > > > Any thoughts are welcome at this point? > > Thanks > > Jaime >
token does not appear to be in SynonymFilterFactory
The solr.SynonymFilterFactory mentions SOLR-319 which is a tokenizerFactory to EdgeGram and then pass it into the SynonymFilterFactory. This does not appear to work. Not sure when it broke? Or maybe the parameters changed? https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.SynonymFilterFactory solr.SynonymFilterFactory Creates SynonymFilter. Matches strings of tokens and replaces them with other strings of tokens. - The *synonyms* parameter names an external file defining the synonyms. - If *ignoreCase* is true, matching will lowercase before checking equality. - If *expand* is true, a synonym will be expanded to all equivalent synonyms. If it is false, all equivalent synonyms will be reduced to the first in the list. - Right here: The optional *tokenizerFactory* parameter names a tokenizer factory class to analyze synonyms (see https://issues.apache.org/jira/browse/SOLR-319), which can help with the synonym+stemming problem described in http://search-lucene.com/m/hg9ri2mDvGk1 . -- Bill Bell billnb...@gmail.com cell 720-256-8076
