StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I think version 3.4 has the most drastic changes since that is when Solr-trunk merged into Lucene trunk making the two repos more in sync. From what I can see from the release notes you have to watch out for one primary thing. Namley the index format has changed so you <strong>definitely need to reindex</strong>. </p> <p>The only other thing I could find relates to no longer ignoring contradictory settings.</p> <p>I would recommend you to just upgrade and try to do a quick reindex. If nothing fails catastrophically you are most likely safe. </p> <p><strong>Including the release notes I checked and some extracts I found interesting:</strong></p> <p><a href="http://svn.apache.org/repos/asf/lucene/solr/tags/release-1.4.0/CHANGES.txt" rel="nofollow">1.4 release notes</a></p> <p><a href="http://svn.apache.org/repos/asf/lucene/java/tags/lucene_solr_3_4_0/solr/CHANGES.txt" rel="nofollow">3.4 release notes</a></p> <ul> <li><p>The Lucene index format has changed and as a result, once you upgrade, previous versions of Solr will no longer be able to read your indices. In a master/slave configuration, all searchers/slaves should be upgraded before the master. If the master were to be updated first, the older searchers would not be able to read the new index format.</p></li> <li><p>Previous versions of Solr silently allow and ignore some contradictory properties specified in schema.xml. For example:</p></li> <li><p>indexed="false" omitNorms="false" </p></li> <li><p>indexed="false" omitTermFreqAndPositions="false"</p> <p>Field property validation has now been fixed, to ensure that contradictions like these now generate error messages. If users have existing schemas that generate one of these new "conflicting 'false' field options for non-indexed field" error messages the conflicting "omit*" properties can safely be removed, or changed to "true" for consistent behavior with previous Solr versions.</p></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload