clintropolis opened a new pull request #12016: URL: https://github.com/apache/druid/pull/12016
### Description This PR adds a fallback mechanism to `DruidSchema` to use the legacy 'type' string field of segment metadata results, after #11895 changed `DruidSchema` to use a new, richer, `typeSignature` field instead. This fixes an issue where the SQL schema for a datasource can be marked entirely as `COMPLEX` typed columns if a broker is updated to 0.23 before historical servers are, and will remain in this state until restarted or all segments have been moved to new servers after all historicals are upgraded. See https://github.com/apache/druid/pull/11713#issuecomment-983269047 for details. This PR has: - [x] been self-reviewed. - [x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader. - [x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for [code coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md) is met. - [x] been tested in a test Druid cluster. -- 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]
