Re: Feedback on Match Query Parser (for fixing multiterm synonyms and other things)

Thanks Alan, that might be doable. What would the outer query look like? A big dismax across the fields with a tie parameter? (ala Elasticsearch most/best fields)? If you did that, you'd probably also want to control the query parser's behavior per field. For example, one field you want to

Re: Blank/Null value search in term filter

Hi Kishore, You can employ an impossible token value (say XX) for null values. This can be done via default value update processor factory. You index some placeholder token for null values. fq={!terms f='queryField' separator='|'}A|XX would fetche docs with A or null values. Ahmet On Friday,

Re: ShardDoc.sortFieldValues are not exposed in v5.2.1

On 9/1/2016 12:31 PM, tedsolr wrote: > I'm attempting to perform my own merge of IDs with a MergeStrategy in v5.2.1. > I'm a bit hamstrung because the ShardFieldSortedHitQueue is not public. When > trying to build my own priority queue I found out that the field > sortFieldValues in ShardDoc is

Re: Is it safe to upgrade an existing field to docvalues?

Hi Ronald, Turning on docValues for existing field works in Solr 4. As you mentioned it will use un-inverting method if docValues are nit found on existing document. This all works fine until segments that have documents without docValues merge with segment that have docValues for the field. In

Re: can't seem to get delta imports to work.

On 8/31/2016 1:54 PM, Stahle, Patrick wrote: > I am having problems getting the delta import working. Full import > works fine. I am using current version of solr (6.1). I have been > looking at this pretty much all day and can't find what I am not doing > correctly... I did try the Using query

Re: commit it taking 1300 ms

It would be worth looking into iostats of your disks. On Aug 22, 2016 10:11 AM, "Alessandro Benedetti" wrote: > I agree with the suggestions so far. > The cache auto-warming doesn't seem the problem as the index is not massive > and the auto-warm is for only 10 docs. >

RE: Always add the marker when elevating documents

Thank you Emir. Alexandre Drouin -Original Message- From: Emir Arnautovic [mailto:emir.arnauto...@sematext.com] Sent: September 2, 2016 5:32 AM To: solr-user@lucene.apache.org Subject: Re: Always add the marker when elevating documents Importance: High Hi Alexandre, You can specify

Re: Use function in condition

Hi Emir, Thank you for your response. Yes your request is working but only if it's function queries. If you mix function query with normal query, this will not work. For example:  fq={!frange l=1}and(query($sub1),or(query($sub2),query($sub3)))=F3:Active={!frange u=2000}sum(F3,F4)={!frange

Blank/Null value search in term filter

Hi, We are using solr 5.4.1. We are using term filter for multiple value matching purpose. Example: fq={!terms f='queryField' separator='|'}A|B A, B, C are the possible field values for solr field "queryField". There can docs with null values for the same field. Now, how can I create a term

SOLR replication: different behavior for network cut off vs. machine restart

Hi, We try to set up a SOLR Cloud environment using 1 shard with 2 replicas (1 leader). The replicas are managed by 3 zookeeper instances. The setup seems fine when we do the normal work. The data is being replicated at runtime. Now we try to simulate erroneous behavior in several cases: Turn

Re: Always add the marker when elevating documents

Hi Alexandre, You can specify default fl paramter for search handler in Solr config. You can use *,[elevated] to return all fields + elevated, but it is recommended to limit fl to fields needed - if you truly need all fields, then using * is ok. Regards, Emir On 01.09.2016 22:11,

Re: Replication Index fetch failed

Hi I cannot find a string in the logs matching "Could not download file...". This info is logged on the slave: WARN - 2016-09-02 09:28:36.923; [c:intradesk s:shard10 r:core_node23 x:intradesk_shard10_replica1] org.apache.solr.handler.IndexFetcher$FileFetcher; Error in fetching file:

Re: How can I set the defaultOperator to be AND?

Thanks Steve for your advice (i.e.: upgrade to Solr 6.2). I finally had time to upgrade and can now use "=AND" together with "=a OR b" and this works as expected. I even defined the following line in the defaults settings in the requestHandler, to overwrite the default behavior: AND Issue

Re: Feedback on Match Query Parser (for fixing multiterm synonyms and other things)

This looks very useful! It would be nice if you could also query multiple fields at the same time, to give more edismax-like functionality. In fact, you could probably extend this slightly to almost entirely replace edismax, by allowing multiple fields and multiple analysis paths. Alan