capistrant commented on pull request #8803: URL: https://github.com/apache/druid/pull/8803#issuecomment-687843802
I think a change like this should have more visibility in release notes in the future. This has the ability to break ingestion jobs that worked in previous versions of druid if they relied on the legacy parser. Any way to retroactively make updates to the druid 17 release notes to call out the new parser coming into play? I'm sure it would save someone the pain that my team felt when our clients started seeing their ingestion jobs start failing after our recent upgrade from druid 15 to druid 18. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
