janhoy commented on code in PR #4187: URL: https://github.com/apache/solr/pull/4187#discussion_r2884049100
########## solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc: ########## @@ -187,17 +198,15 @@ Nowadays, the HTTP request is available via internal APIs: `SolrQueryRequest.get * The TieredMergePolicy's segmentsPerTier default changed to `8` but `10` may be configured to retain prior behaviour. (SOLR-17917). -* BlobHandler and the `.system` collection have been removed in favour of FileStore API. (SOLR-17851). - * The deprecated transient Solr cores capability has been removed. (SOLR-17932) * TikaLanguageIdentifierUpdateProcessor, which was deprecated in 9.10, has been removed. Users should use LangDetectLanguageIdentifierUpdateProcessor or OpenNLPLangDetectUpdateProcessor instead for language detection. (SOLR-17960) * LocalTikaExtractionBackend, which was deprecated in 9.10, has been removed. The 'tikaserver' extraction backend is now the only supported backend for the ExtractingRequestHandler, and the default. Users must configure a Tika Server URL via the `tikaserver.url` parameter. (SOLR-17961) -+NOTE: The previous parse-context-based configuration (`parseContext.config`) is no longer supported. Tika parser-specific properties must now be configured directly on the Tika Server itself, rather than through Solr configuration. Please refer to the Tika Server documentation for details on how to set these properties. +NOTE: The previous parse-context-based configuration (`parseContext.config`) is no longer supported. Tika parser-specific properties must now be configured directly on the Tika Server itself, rather than through Solr configuration. Please refer to the Tika Server documentation for details on how to set these properties. Review Comment: I wrote it so I should know :-) It is definitely related and it looks weird to have a `NOTE` block in the middle of a bullet-list. Let me explicitly inline the NOTE in the prev. bullet -- 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]
