},
      "fess_korean_normal": {
        "type": "nori_tokenizer",
        "decompound_mode": "mixed",
        "user_dictionary_rules": ["덕후", "버카충", "낄끼빠빠" ]
      }
    },
    "analyzer" : {
      "reading_analyzer" : {
        "type" : "custom",
        "tokenizer" : "fess_japanese_normal",
        "filter" : ["reading_form"]
      },
      "reading_term_analyzer" : {
        "type" : "custom",

        "mode" : "normal",
        "discard_punctuation" : "false"
      },
      "pattern_split" : {
        "type" : "simple_pattern_split",
        "pattern" : "__and__"
      }
    },
    "analyzer" : {
      "reading_analyzer" : {
        "type" : "custom",
        "tokenizer" : "kuromoji_neologd_normal",
        "filter" : ["reading_form"]
      },
      "reading_term_analyzer" : {
        "type" : "custom",

            encountered during execution, an exception will be raised with
            information about the incompatible ops.
    *   Add lite.experimental.Analyzer API
        *   An experimental tool to analyze TFLite flatbuffer models. This API
            can be used to investigate TFLite model structure and check
            compatibility with GPU delegate.

*   Extension Types

  --data-binary @fess-documents.json
```

#### Index Settings Migration

Fess uses OpenSearch/Elasticsearch internally, so you can:

1. Export index mappings and settings from source
2. Apply custom analyzers in Fess's `fess_config.properties`
3. Create synonym dictionaries in Fess's dictionary directory

---

### Apache Solr

For migrating from Apache Solr:

#### Document Export and Import

     * Get the value for the key 'query.additional.analyzed.fields'. <br>
     * The value is, e.g.  <br>
     * comment: Additional analyzed fields for queries.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getQueryAdditionalAnalyzedFields();

    /**
     * Get the value for the key 'query.additional.analyzed.fields' as {@link Integer}. <br>

            "user_dictionary_rules": ["덕후", "버카충", "낄끼빠빠" ]
        },
        "simplified_chinese_tokenizer": {
            "type": "smartcn_tokenizer"
        }
      },
      "analyzer": {
        "arabic_analyzer": {
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "arabic_stop",

            "user_dictionary_rules": ["덕후", "버카충", "낄끼빠빠" ]
        },
        "simplified_chinese_tokenizer": {
            "type": "smartcn_tokenizer"
        }
      },
      "analyzer": {
        "arabic_analyzer": {
          "type": "custom",
          "tokenizer": "standard",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "arabic_stop",

order to a compiler.
</p>

<p>
Dependency analysis does not rely on the actual values of the
variables, only on lexical <i>references</i> to them in the source,
analyzed transitively. For instance, if a variable <code>x</code>'s
initialization expression refers to a function whose body refers to
variable <code>y</code> then <code>x</code> depends on <code>y</code>.
Specifically:
</p>