*/
public class SynonymCreator extends DictionaryCreator {
    private static final Logger logger = LogManager.getLogger(SynonymCreator.class);

    /**
     * Constructs a new creator for synonym dictionaries.
     * It sets the file pattern to match files starting with "synonym"
     * and ending with ".txt".
     */
    public SynonymCreator() {
        super("synonym.*\\.txt");
    }

    /**

      "sv_analyzer": {
        "type": "custom",
        "tokenizer": "standard",
        "filter": ["lowercase", "swedish_stop", "swedish_stemmer"]
      }
    }
  }
}
```

### 2. Add Custom Dictionaries (Optional)

Create custom dictionary files in: `${fess.dictionary.path}/[lang]/`

Available dictionary types:
- `stopwords.txt` - Words to exclude from indexing
- `stemmer_override.txt` - Custom stemming rules

import org.dbflute.optional.OptionalEntity;

import jakarta.annotation.Resource;

/**
 * Service for managing stopwords.
 * This class provides methods to interact with stopwords dictionaries,
 * including retrieving, storing, and deleting stopwords.
 */
public class StopwordsService {
    /** The dictionary manager for accessing dictionary files. */
    @Resource

import org.dbflute.optional.OptionalEntity;

import jakarta.annotation.Resource;

/**
 * Service for managing synonyms.
 * This class provides methods to interact with synonym dictionaries,
 * including retrieving, storing, and deleting synonyms.
 */
public class SynonymService {
    /** The dictionary manager for accessing dictionary files. */
    @Resource

/**
 * Represents a single character mapping rule that defines how input characters are mapped to output characters
 * for text analysis and search processing. This class is used in character mapping dictionaries to transform
 * text during indexing and search operations.
 *
 * <p>Each mapping item consists of one or more input character sequences that are mapped to a single output

import jakarta.servlet.ServletContext;

/**
 * Utility class for accessing various resource paths and files in the Fess application.
 * This class provides methods to retrieve paths for configuration files, templates, dictionaries,
 * thumbnails, plugins, and other resources required by the Fess search engine.
 * It supports both regular deployment and Docker container environments.
 *
 */
public class ResourceUtil {

			 "cluster.initial_cluster_manager_nodes":"search_engine",
			 "node.roles":"cluster_manager,data,ingest,ml",
			 -->
			 "indices.breaker.total.limit":"100%",
			 "action.auto_create_index":"-*"}
		</property>
		<!-- Dictionaries -->
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"mapping.txt"</arg>
		</postConstruct>
		<postConstruct name="addConfigFile">
			<arg>"fess"</arg>
			<arg>"synonym.txt"</arg>

    }

    /**
     * Starts a reindex operation with the specified parameters.
     *
     * @param replaceAliases whether to replace aliases after reindexing
     * @param resetDictionaries whether to reset dictionaries during reindexing
     * @param numberOfShards the number of shards for the new index
     * @param autoExpandReplicas the auto expand replicas setting for the new index

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

**Step 1: Export from Solr**

```bash

labels.upgrade_data_migration=Data Migration
labels.upgrade_reindex=Re-indexing
labels.upgrade_start_button=Start
labels.replace_aliases=Replace Aliases
labels.reset_dictionaries=Reset Dictionaries
labels.reindex_start_button=Start
labels.targetVersion=Target Version
labels.target_version=Target Version
labels.sereq_configuration=Request to OpenSearch
labels.sereq_request_file=Request File