epugh opened a new pull request, #5370: URL: https://github.com/apache/solr/pull/5370
https://issues.apache.org/jira/browse/SOLR-11033 ## Description Move built-in language-specific text analysis out of `_default` into a new `_multilingual` configset. New collections using `_default` get general-purpose field types; collections needing types such as `text_en` or dynamic fields such as `*_txt_fr` can select `_multilingual`. Existing ZooKeeper configsets and collections remain unchanged. Related: #971. This branch contains one feature commit directly on current main. ## Solution - Move language-specific field types, dynamic fields, and supporting files into `_multilingual`, using the current schemas and dictionaries. - Bootstrap `_multilingual` when installed locally and absent from ZooKeeper, preserving existing configsets. - Let Schema Designer restore selected languages from `_multilingual` while preserving custom source definitions and files. Generic schema editing also works when `_multilingual` is absent. - Ship only `_default` in the slim distribution; include `_multilingual` and the techproducts configset in the full distribution. - Update Schema Designer help, the reference guide, Solr 11 upgrade notes, and the changelog. Developed with assistance from OpenAI Codex. ## Tests - `./gradlew tidy` and `./gradlew check -x test` passed. - Focused Java suites covering configset services, Schema Designer, configset APIs, ZooKeeper reads, and CoreContainer: 58 tests, 3 skipped. - Packaged CATS `CreateCollectionTest` and `ZkTest`: all 24 tests passed, including creating a `_multilingual` collection and indexing and querying French text. - Built and inspected both distribution archives: slim contains only `_default`; full contains `_default`, `_multilingual`, and `sample_techproducts_configs`. The clean branch has the identical source tree to the implementation used for these checks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
