+1 to always version the output format ________________________________ From: Dinesh Joshi <djo...@apache.org> Sent: Thursday, July 13, 2023 3:36 PM To: dev <dev@cassandra.apache.org> Subject: [EXTERNAL] Re: Changing the output of tooling between majors
This adds maintenance overhead but is a potential alternative. I would only flip the flag. I would prefer to make the default "legacy" output and innovate behind a "--output-format=v2" flag. That way tools do not break or have to change to pass in the new flag. Ideally we should always version our output format - structured or not. Dinesh On Jul 13, 2023, at 9:08 AM, German Eichberger via dev <dev@cassandra.apache.org> wrote: Let's take this discussion in a different direction: If we add a --legacy <version> argument where we are supporting an old version for those who need/want it but have the (breaking) changes on the default this feels like a compromise - and then we can deprecate the legacy format without impacting innovation. We can also flip this with requiring a flag for the changed format if we feel this is better. This let's us innovate without breaking anyone. Thoughts? Thanks, German
