clintropolis commented on pull request #11713: URL: https://github.com/apache/druid/pull/11713#issuecomment-983369913
> Yes, the cluster has be updated fully. Are the types still incorrect in your cluster? The issue I mentioned I think would be temporary, though I guess it could take some time before the issue corrects itself because it populates reactively, but I think could be resolve immediately by restarting the brokers > If the order of upgrading is overlord -> coordinator -> historical -> middle-manager -> broker -> router, can this compatibility problem be avoided I did a fair bit of compatibility testing around upgrade order so I believe so, though the bulk of it was before #11895 went in, which is the change that added a new field to the segment metadata query response to populate the types in `DruidSchema`. -- 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]
