Re: Why do I get different results for the same query with two Solr versions?
Tulsi wrote > Can you post the managed schema and solrconfig content here ? Schema for the 4.6 index (I omitted all non-relevant data): Schema for the 7.5 index (I omitted all non-relevant data): About the solrconfig.xml file - I don't think I can share it because it may contain sensitive information. Is there something specific from this file that may be relevant for our discussion? Tulsi wrote > Do try the solr admin analysis screen > once as well to see the behaviour for this field. > https://lucene.apache.org/solr/guide/7_6/index.html I looked at the analysis screen, but it wasn't helpful. That's why I started using the "debug=query" parameter and the content of parsedquery. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Re:Re: Why do I get different results for the same query with two Solr versions?
Hi, thank for the comment, but I tried to use both "sow=false" and "saw=true" and I still get the same result. For query (TITLE_ItemCode_t:KI_7) I still see: Solr 4.6: "parsedquery": "PhraseQuery(TITLE_ItemCode_t:\"ki 7\")" Solr 7.5: "parsedquery":"+(+(TITLE_ItemCode_t:ki7 (+TITLE_ItemCode_t:ki +TITLE_ItemCode_t:7)))" Tulsi wrote > Hi , > Yes this look like related to sow (split on whitespace) param default > behaviour change in solr 7. > > The sow parameter (short for "Split on Whitespace") now defaults to > false, which allows support for multi-word synonyms out of the box. > This parameter is used with the eDismax and standard/"lucene" query > parsers. If this parameter is not explicitly specified as true, query > text will not be split on whitespace before analysis. > > https://lucene.apache.org/solr/guide/7_0/major-changes-in-solr-7.html > > > On Sun, 27 Dec, 2020, 8:25 pm nettadalet, > nsteinberg@ > wrote: > >> I added "defType=lucene" to both searches to make sure I use the same >> query >> parser, but it didn't change the results. >> >> >> >> -- >> Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html >> -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Re:Re: Why do I get different results for the same query with two Solr versions?
I added "defType=lucene" to both searches to make sure I use the same query parser, but it didn't change the results. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Re:Re: Why do I get different results for the same query with two Solr versions?
I'm not sure how to check the implementation of the query parser, or how to change the query parser that I use. I think I'm using the standard query parser. I use Solr Admin to run the queries. If I look at the URL, I see Solr 4.6: select?q=TITLE_ItemCode_t:KI_7=TITLE_ItemCode_t Solr 7.5: select?q=TITLE_ItemCode_t:KI_7=TITLE_ItemCode_t Should I change something? Where should I look? -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Why do I get different results for the same query with two Solr versions?
Thank you, that was helpful! For Solr 4.6 I get "parsedquery": "PhraseQuery(TITLE_ItemCode_t:\"ki 7\")" For Solr 7.5 I get "parsedquery":"+(+(TITLE_ItemCode_t:ki7 (+TITLE_ItemCode_t:ki +TITLE_ItemCode_t:7)))" So this is the cause of the difference in the search result, but I still don't know why the parsedquery is different between the two versions. Any idea/guess? Is it some internal implementation that changed sometime between 4.6 and 7.5? -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Why do I get different results for the same query with two Solr versions?
Hello, I have the the same field type defined in Solr 4.6 and Solr 7.5. When I search with both versions, I get different results, and I don't know why I have the following *field type definition in Solr 4.6*: I have the following *field type definition in Solr 7.5*: * I tried to use solr.WordDelimiterFilterFactory with Solr 7.5 instead of solr.WordDelimiterGraphFilterFactory so the field types will be more alike, but the result was the same. I have the following *6 values set for field text1 of type text_type1 for 6 different documents* (the type(s) from above): KI_d5e7b43a KI_b7c490bd KI_7df2f026 KI_fa7d129d KI_5867aec7 KI_7c3c0b93 My query is *text1=KI_7*. Using Solr 4.6, I get 2 result - KI_7df2f026, KI_7c3c0b93 Using Solr 7.5, I get all 6 results. Questions: 1. How come I get different results with the same data, when my fields definitions are the same (as far as I can tell)? 2. What are the expected results? I think that the results Solr 7.5 returns are the correct ones, since at the end of the of the analysis I get *KA* as a term and *7* as a term, both during the indexing analysis and the query analysis, so, to my understanding, all 6 results should be found. Is this correct? if not, what am I missing? what don't I understand correctly? I would very much appreciate a full/partial answer, but even a link that could explain at least the expected results part would be great. Thanks in advance, I know this might be a tough one to answer [Hope not :)] -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Is there a way to search for "..." (three dots)?
Hi, I need to be able to search for "..." (three dots), meaning the query should be "..." and the search should return results that have "..." in their names. Is there a way to do it? Thanks in advance. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Corrupted .cfs file
Sorry to reply just now, but you were right - the problem was that the disk got full. Thank you very much! -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Corrupted .cfs file
I get the following exception: Caused by: org.apache.lucene.index.CorruptIndexException: length should be 104004663 bytes, but is 104856631 instead (resource=MMapIndexInput(path="path_to_index\index\_jlp.cfs")) What may be the cause of this? How can the length of the .cfs file change so it become corrupted? Can I simply delete this .cfs file and then synchronized the index against the database, so only the missing files will be indexed, instead of reindexing all the files? Thanks in advance. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Does an empty query value can cause an "org.apache.solr.search.SyntaxError" error?
Shawn Heisey-2 wrote > I don't know whether that actually is written anywhere. I suspect it's > not. > > I do think that it is proper for empty parentheses to throw a syntax > error. The text of the exception message is saying that the parser > encountered the ) character at a point when it did not expect to > encounter that character. > > Thanks, > Shawn Thank you for your answer -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Does an empty query value can cause an "org.apache.solr.search.SyntaxError" error?
Shawn Heisey-2 wrote > I don't know whether that actually is written anywhere. I suspect it's > not. > > I do think that it is proper for empty parentheses to throw a syntax > error. The text of the exception message is saying that the parser > encountered the ) character at a point when it did not expect to > encounter that character. > > Thanks, > Shawn Thank you for your answer -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Does an empty query value can cause an "org.apache.solr.search.SyntaxError" error?
We are using Solr 4.6 (yes, I know. We plan an update in the near future) I get the following error: org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError: Cannot parse '((TITLE_Name_t:( la verita))) AND ((TITLE_Artist_t:( ))) AND (TITLE_Type_e : "Audio")': Encountered " ")" ") "" at line 1, column 53. I think it is because of the TITLE_Artist_t:( ) It happens even when I change it to TITLE_Artist_t:() but when I add some string inside the parenthesis (i.e. TITLE_Artist_t:(abc)), it works fine. Can anyone show me if and where it is written that an empty value can cause an org.apache.solr.search.SyntaxError? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
