protected final String contentsAnalyzer;
        /** Contents reading analyzer name. */
        protected final String contentsReadingAnalyzer;

        /**
         * Constructor.
         * @param readingAnalyzer Reading analyzer name
         * @param readingTermAnalyzer Reading term analyzer name
         * @param normalizeAnalyzer Normalize analyzer name
         * @param contentsAnalyzer Contents analyzer name

import org.codelibs.fess.suggest.normalizer.ICUNormalizer;

// Configure custom settings
SuggestSettings settings = SuggestSettings.builder()
    .analyzer(analyzers -> {
        // Configure custom analyzers
        analyzers.addAnalyzer("custom", customAnalyzerSettings);
    })
    .build();

Suggester customSuggester = Suggester.builder()
    .settings(settings)

                .put("analysis.analyzer.test_reading_analyzer_ja.type", "custom")
                .put("analysis.analyzer.test_reading_analyzer_ja.tokenizer", "keyword")
                .put("analysis.analyzer.test_reading_term_analyzer_ja.type", "custom")
                .put("analysis.analyzer.test_reading_term_analyzer_ja.tokenizer", "keyword")
                .build();

4. Applies language-specific analyzers for better search results

Configured in `fess_config.properties`:
```properties
indexer.language.fields=content,important_content,title
```

## Optional: Search Analysis Support

If your language requires special text analysis (stemming, stop words, etc.), you may need to configure OpenSearch analyzers.

### 1. Update OpenSearch Index Template

        SuggestAnalyzer analyzer = suggester.settings().analyzer().new DefaultContentsAnalyzer();
        String text = "これはテストです。検索エンジン。";

        List<AnalyzeToken> tokens = defaultContentsParser.analyzeTextByReading(analyzer, "content", text, null);

        assertNotNull(tokens);
        // analyzeAndReading may return null for some analyzers
        // Just verify it doesn't throw an exception
    }

  --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

        // Test that multiple analyzer instances work independently
        SuggestAnalyzer analyzer1 = new TestSuggestAnalyzer();
        SuggestAnalyzer analyzer2 = new TestSuggestAnalyzer();

        String text = "test text";
        String field = "content";
        String lang = "en";

        List<AnalyzeToken> tokens1 = analyzer1.analyze(text, field, lang);

    }

    /**
     * Analyze text.
     * @param analyzer Analyzer
     * @param field Field
     * @param text Text
     * @param lang Language
     * @return List of tokens
     */
    protected List<AnalyzeToken> analyzeText(final SuggestAnalyzer analyzer, final String field, final String text, final String lang) {
        return analyzeTextInternal(analyzer, field, text, lang, false);
    }

    /**

import org.apache.maven.model.v4.MavenStaxReader;

/**
 * A utility class that analyzes Maven POM files to identify memory usage patterns and potential memory optimizations.
 * This analyzer focuses on identifying duplicate strings and their memory impact across different paths in the POM structure.
 *
 * <p>The analyzer processes POM files recursively, tracking string occurrences and their locations within the POM structure.

        this.defaultField = defaultField;
    }

    /**
     * Sets the analyzer used to analyze query terms.
     *
     * @param analyzer the analyzer to use
     */
    public void setAnalyzer(final Analyzer analyzer) {
        this.analyzer = analyzer;
    }

    /**
     * Sets whether to allow leading wildcards in query terms.
     *