For example, the 'ignoreCase' argument expects a value "true" rather than "1" in exported schema_extra_types.xml, because the value "1" will be parsed to value false in java: https://github.com/apache/lucene-solr/blob/master/lucene/analysis/common...
<filter class="solr.StopFilterFactory" ignoreCase="1" words="stopwords_en.txt"/>
should be:
<filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords_en.txt"/>
The same to 'onlyLongestMatch', 'expand' and 'concat' arguments.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2933293-2.patch | 52.2 KB | edaa |
Comments
Comment #2
edaa commentedAdd a patch
Comment #3
edaa commentedThe major changes in above patch:
Comment #4
mkalkbrennerThanks for pointing that out!
But the proposed fix is wrong, because we'll lose drupal's schema verification since a string can be anything.
We already have code at various places that coverts drupal booleans to strings. It seems that we missed that when creating the Solr XML config files.
Examples, where the convertion already happens:
SearchApiSolrBackend::formatFilterValue()
SolrFieldTypeListBuilder::getSchemaExtraFieldsXml()
I think we should adjust SolrFieldType::buildXmlFromArray() accordingly.
Comment #5
edaa commentedThanks, I didn't notice the convertion already happens. So closed it.
Comment #6
mkalkbrennerI re-open it as a reminder that I have to check all the places. I'm not sure that we covered all places.
Comment #7
mkalkbrenner