FrankChen021 commented on PR #20228: URL: https://github.com/apache/druid/pull/20228#issuecomment-5550991406
> > However, that support was for decompressing externally supplied .zst files. Druid still documents zst as a supported batch-ingestion format, and the current path delegates these files to zstd-jni. > > Fair, I guess it just seems unfortunate to block upgrades on stuff because we can't read hypothetical batch input files that would likely have been written with a version more than 10 years old at this point. I think i'd be in favor of just calling this out in release notes and telling people to re-encode their files prior to ingest if they run into problems, but I am interested in others opinions as well. We can do that. But for us, we can't ask users to re-encode old files only when they encounter the problem. And if such problem happens, I don't think it's easy to re-encode old files, because users take time to upgrade their data pipelines to use newer zstd encoders. And such upgrading may also bring some concerns because these files are not only used by druid only. My opinion is that if there's no severe CVEs on 1.5.7.11 or there're no new features we must to use in newer releases, let's keep using it. -- 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]
