Marius Grama created SOLR-7679: ---------------------------------- Summary: Schema API doesn't take similarity attribute into account when adding field types Key: SOLR-7679 URL: https://issues.apache.org/jira/browse/SOLR-7679 Project: Solr Issue Type: Bug Components: Schema and Analysis Affects Versions: 5.2 Reporter: Marius Grama Priority: Minor Fix For: 5.3, Trunk
When using the request {code} curl -X POST -H 'Content-type:application/json' --data-binary '{ "add-field-type": { "name": "fieldTypeWithSimilarity", "class": "org.apache.solr.schema.TextField", "analyzer": { "charFilters": [ { "class": "solr.PatternReplaceCharFilterFactory", "replacement": "$1$1", "pattern": "([a-zA-Z])\\\\1+" } ], "tokenizer": { "class": "solr.WhitespaceTokenizerFactory" } }, "similarity": { "class": "org.apache.lucene.misc.SweetSpotSimilarity" } } }' http://localhost:8983/solr/gettingstarted/schema {code} can be seen in the updated schema.xml that the similarity attributes for the newly added field type doesn't contain a _similarity_ entry. This is due to the fact that within FieldTypeXmlAdapter the similiarity element is not being added to the field type. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org