I'm migrating from 3.x to 4.x and I'm running some queries to verify that
everything works like before. I've found however that the query galaxy s3
is giving much less results. In 3.x numFound=1628, in 4.x numFound=70.
Here's the relevant schema part:
fieldtype name=text_pt class=solr.TextField
: I'm migrating from 3.x to 4.x and I'm running some queries to verify that
: everything works like before. I've found however that the query galaxy s3
: is giving much less results. In 3.x numFound=1628, in 4.x numFound=70.
is your entire schema 100% identical in both cases?
what is the
checking why that was so since we'll be moving away from
the older version, which shows the inconsistency.
But thanks a million.
If you have a SO user I can mark yours as answer here:
http://stackoverflow.com/questions/18661996/solr-4-x-vs-3-x-parsedquery-differences
Cheers
On Sep 6, 2013 4:15 PM
: Our schema is identical except the version.
: In 3.x it's 1.1 and in 4.x it's 1.5.
That's kind of a significant difference to leave out -- indepenent of the
question you are asking about here, it's going to make quite a few
differences in how things are being being parsed, and what defaults
On 9/6/2013 12:46 PM, Fermin Silva wrote:
Our schema is identical except the version.
In 3.x it's 1.1 and in 4.x it's 1.5.
Also in solrconfig.xml we have no lucene version for 3.x (so it's using 2_4
i believe) and in 4.x we fixed it to 4_4.
The autoGeneratePhraseQueries parameter didn't exist
Hi,
Our schema is identical except the version.
In 3.x it's 1.1 and in 4.x it's 1.5.
Also in solrconfig.xml we have no lucene version for 3.x (so it's using 2_4
i believe) and in 4.x we fixed it to 4_4.
Thanks
On Sep 6, 2013 3:34 PM, Chris Hostetter hossman_luc...@fucit.org wrote:
: I'm
