#793 closed defect (fixed)
VLO SOLR configuration doesnt work for SOLR version 5.3
| Reported by: | davor.ostojic@oeaw.ac.at | Owned by: | teckart@informatik.uni-leipzig.de |
|---|---|---|---|
| Priority: | minor | Milestone: | VLO-3.4 |
| Component: | VLO importer | Version: | |
| Keywords: | Cc: | Twan Goosen |
Description
When SOLR version was updated to 5.3, problem was experienced with schema.xml configuration. Solr could not be started because of:
<filter class="solr.CollationKeyFilterFactory?" custom="customCollationRules.bin" strength="primary"/>
Change History (8)
comment:1 Changed 9 years ago by
| Cc: | Twan Goosen added |
|---|
comment:2 Changed 9 years ago by
comment:3 Changed 9 years ago by
Decided to be put on '3.5 or later' milestone in developer video conference
comment:4 Changed 9 years ago by
Reason is that CollationKeyFilterFactory? is deprecated in 4.x and got removed in 5.x. CollationKeyAnalyzer? should be used instead. Unfortunately so far I was not able to find an example configuration for the new class.
comment:5 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Removed the CollationKeyFilter? from schema.xml (r6713). Some checks showed that the filter lead to unsatifying result sets for queries with Umlaute (also related to #545)
comment:8 Changed 8 years ago by
| Milestone: | VLO-4.1 or later → VLO-3.4 |
|---|
Note: See
TracTickets for help on using
tickets.
IIRC this filter was added because of problems with German Umlaute (ae -> ä, oe -> ö) etc.. As this can also be achieved by using system collations for the specific language, a different approach would be to replace this line with:
Could you check if this still leads to problems with Solr 5.3?