Re: Excluding a block join filter query during faceting

Why do you think it doesn't work? &fq={!parent tag=test which="my_doc_type:Parent"}child_doc_some_field:("30") On Wed, Dec 4, 2019 at 12:38 AM Srijan wrote: > I was wondering if anyone has encountered this problem. > > I have a parent block join query to return parent documents when child > docu

Re: [Q] Faster Atomic Updates - use docValues?

Hi Erick, Thank you for replying. Do you have empirical evidence that all these parameter changes are doing > you any good? When I had played with merge configuration last year, the new values gave an instant boost to indexing (but I could only test for the first few thousand documents). Incre

Re: NPE on exceeding timeAllowed on SOLR-8.1.1

Hi, this is an issue (or a variation of it) that we encountered when using timeAllowed since we started using Solr (5 or 6). I see that there's a couple of JIRA issues that cover similar problems e.g. https://issues.apache.org/jira/browse/SOLR-9882 which is marked as resolved in 8.1. It's possible

Re: Is it possible to have different Stop words depending on the value of a field?

Hi, I’ve spent quite a lot time working on a similar issue but I did not think about it much since (at the time it was Solr 1.3) so some new features could push me to some other direction, but here is what I remember: You cannot rely on users entering standardised address format even within one

Re: Excluding a block join filter query during faceting

Oh wow, I feel stupid. I was trying {*!parent* which="my_doc_type:Parent" *!tag*=test}. Thanks a lot. On Wed, Dec 4, 2019, 03:11 Mikhail Khludnev wrote: > Why do you think it doesn't work? > &fq={!parent tag=test > which="my_doc_type:Parent"}child_doc_some_field:("30") > > On Wed, Dec 4, 2019 at

q.op=AND vs default (q.op=OR)

Dear reader, I'm using solr 8.1.1. I'm trying to switch from q.op=OR to q.op=AND, because of the parser I generate the queries for solr is somewhat more simple to develop with q.op=AND. but the new query is returning less hits; I have shortened the query string for better readability; _g_up

Re: [ANNOUNCE] Apache Solr 8.3.1 released

Thanks ishan On Wed, Dec 4, 2019, 3:32 PM Ishan Chattopadhyaya wrote: > ## 3 December 2019, Apache Solr™ 8.3.1 available > > The Lucene PMC is pleased to announce the release of Apache Solr 8.3.1. > > Solr is the popular, blazing fast, open source NoSQL search platform > from the Apache Lucene p

Re: q.op=AND vs default (q.op=OR)

Found https://cwiki.apache.org/confluence/display/lucene/BooleanQuerySyntax But this does not explain the problem... Oh... and there is a bug in the abbreviated queries: the X behind the second _g_dn should be Y - but this does not affect the further AND/OR/+/- query structure. Jochen Am 0

WITHDRAWN! Re: q.op=AND vs default (q.op=OR)

Mea culpa ... ran the different queries against two different solr instances. Everything works fine. Kind regards, Jochen Am 04.12.19 um 13:20 schrieb Jochen Barth: Found https://cwiki.apache.org/confluence/display/lucene/BooleanQuerySyntax But this does not explain the problem... Oh... an

Re: Exact match

Hi, Here's our example of exact match fields: https://github.com/NatLibFi/finna-solr/blob/master/vufind/biblio/conf/schema.xml#L48 textProper_l requires a partial match from the beginning. textProper_lr requires a full match. I'm not sure if this works for you, but at least we have this creative

Re: [ANNOUNCE] Apache Solr 8.3.1 released

Thanks Ishan. I was just going through the list of fixes in 8.3.1 (published in changes.txt) and couldn't see the below JIRA. SOLR-13971 : Velocity response writer's resource loading now possible only through startup parameters. Is it linked approp

Re: [Q] Faster Atomic Updates - use docValues?

This is a huge red flag to me: "(but I could only test for the first few thousand documents” You’re probably right that that would speed things up, but pretty soon when you’re indexing your entire corpus there are lots of other considerations. The indexing rate you’re seeing is abysmal unless t

Searching a nested structure. Can not retrieve parents with all corresponding childs

Hi there, I have problems retrieving data in the nested structure in that it is indexed in solr 8.2: I have a product database with products as the parent element and size/color combinations as the child elements. The data is imported with the data import handler:

SpanFirst vs SpanEnd

Hi, After deep diving into lucene code I found that, the SpanFirstQuery object just use the SpanPositionRangeQuery object with start position 0 and the given end position from the query. I am trying to implement the SpanEndQuery in the same way because the End position should be the last posit

updating resourcename (metadata) after renaming of the file

Hi,     I'm new to solr and my question might seems to be dumb. Please bear with me.     In short, if a file (after indexed by solr) changed its name, could I only update resourcename and keep all other information the same in the index? Or do I have to delete it and then re-index the file?     

Re: updating resourcename (metadata) after renaming of the file

I think this is the one you are looking for: http://yonik.com/solr/atomic-updates/ On Wed, Dec 4, 2019 at 9:40 AM Nan Yu wrote: > Hi, I'm new to solr and my question might seems to be dumb. Please > bear with me. > In short, if a file (after indexed by solr) changed its name, could I > o

Re: updating resourcename (metadata) after renaming of the file

Hi, Rui Niu:Thanks for your help! I tried that but it did not work for the "resourcename". The reason might be the "resourcename" is a "metadata" field that generated by Tika (SimplePostTool). Not a user specified field (such as "author_s" in the link you provided). The method you recommended do

HTTP Error 500 - Problem accessing /solr/

Hi, We installed Solr 7.6 and Zookeeper 3.4.14 on a Linux OS. When we were enabling SSL on Solr and ran the following command to configure Zookeeper: server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181 -cmd clusterprop -name urlScheme -val https We are now getting this 500 error on t

Re: HTTP Error 500 - Problem accessing /solr/

You need to go to your solr logs in this case, usually there’s a much better stack trace there about what really went wrong. By the time the error gets percolated back up to the client, some of the information is usually lots. look for “Caused by” in your solr logs and post the entire stack trac

Re: [Q] Faster Atomic Updates - use docValues?

Hey Erick, This is a huge red flag to me: "(but I could only test for the first few > thousand documents”. Yup, that's probably where the culprit lies. I could only test for the starting batch because I had to wait for a day to actually compare. I tweaked the merge values and kept whatever gave

Re: [ANNOUNCE] Apache Solr 8.3.1 released

Hey Ishan, Cannot find 8.3.1 here: https://lucene.apache.org/solr/downloads.html (8.3.0 is listed here). Anyways, I'm downloading it from here: https://archive.apache.org/dist/lucene/solr/8.3.1/ On Wed, 4 Dec 2019 at 20:27, Rahul Goswami wrote: > Thanks Ishan. I was just going through the li