[SOLR-7679] Schema API doesn't take similarity attribute into account when adding field types

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2
• Fix Version/s: 5.3, 6.0
• Component/s: Schema and Analysis
• Assignee: Steven Rowe
• Reporter: Marius Grama
• Created: 14/Jun/15 21:48
• Updated: 09/May/16 18:46
• Resolved: 19/Jun/15 20:29

Description

When using the request

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

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.

Issue Links

• relates to: SOLR-7182 Make the Schema-API a first class citizen of SolrJ