Re: Limit search queries only to pull replicas

option, though. Not >>>>> everyone uses Solrj, and a typical fairly dummy client just queries the >>>>> server without any understanding about shards etc. Solr could be clever >>>>> enough to not forward the query to NRT shards when configured to prefer >>

Limit search queries only to pull replicas

Hi, We have a Solr 7.1 setup with SolrCloud where we have multiple shards on one server (for indexing) each shard has a pull replica on other servers. What are the possible ways to limit search request only to pull type replicase? At the moment the only solution I found is to append shards para

DocValues and facet searches

Hello everyone, Recently we moved to DocValue fields and now we have a problem when some facet queries doesn’t work at all with facet.method different than enum, I know that enum method is more efficient for such fields than default one anyway, but I'm just curious to find out the reason. Here

Re: Problems with stored/not-stored field filter queries

o get what's going on there. What is $q ? > How it's supposed to work? > > 24 янв. 2017 г. 18:29 пользователь "Stanislav Sandalnikov" < > s.sandalni...@gmail.com> написал: > >> Hi everyone, >> >> I’m facing strange Solr behavior, which

Re: Problems with stored/not-stored field filter queries

it since the field was not stored. By the way is there any way to see if there is a index for some particular field of a document? Stanislav > 24 янв. 2017 г., в 23:43, Shawn Heisey написал(а): > > On 1/24/2017 8:29 AM, Stanislav Sandalnikov wrote: >> With indexed but not s

Problems with stored/not-stored field filter queries

Hi everyone, I’m facing strange Solr behavior, which could be better described in examples: With indexed but not stored IndexDate field: 1) With this query everything works fine, I’m getting the results back: /select?fl=taskid,docid,score&q=*:*&fq=category:"Security")))+AND+(datasource:(sit

SolrCloud Term Vectors NullPointerException

Hello everyone, I have problems with setting up SolrCloud to work with term vectors, failing with error: java.lang.NullPointerException at org.apache.solr.handler.component.TermVectorComponent.finishStage(TermVectorComponent.java:437) at org.apache.solr.handler.component.SearchHandler.handleReq

TermVector and Sharding issue

Hello everyone, I saw that the ticket regarding this issue is still open ( https://issues.apache.org/jira/browse/SOLR-4479). There is last comment that suggests to reindex documents with solr 4.2. I did reindex with 4.3 version but term vector still doesn't work producing null pointer exception.

Re: Search performance: shards or replications?

to benchmark your setup varying the load so that you case > trace a hockey stick graph of Qtime versus qps. > Feel free to ask for details if needed. > > > > André > > On 05/07/2013 01:56 PM, Stanislav Sandalnikov wrote: > >> Hi Yan, >> >> Thanks for the qu

Re: Search performance: shards or replications?

P.S. Sorry for misspelling your name, Jan 2013/5/7 Stanislav Sandalnikov > Hi Yan, > > Thanks for the quick reply. > > Thus, replication seems to be the preferable solution. QTime decreases > proportional to replications number or there are any other drawbacks? > > Just

Re: Search performance: shards or replications?

ou add some extra overhead with sharding as well. > > But if your QPS is moderate and you have tons of documents, you may gain > better performance both for indexing latency and search latency by > sharding. > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.