etseidl commented on PR #11262: URL: https://github.com/apache/arrow-rs/pull/11262#issuecomment-5956995188
Sorry @HippoBaro, I've been too consumed with my footer adventures to loop back to this. As to the compatibility question, in the past when we've been in the wrong on the encoding side, we've been very conservative on the read side. If possible, it would be nice to be able to read both forms, but only write the correct one moving forward. We'd want to document in the code why both read paths are allowed, and maybe note in the docs that for compatibility reasons we'll accept the broken files, but that support may eventually go away. If it's not really feasible to support two read paths, then I'm not sure what to do. We really shouldn't keep writing non-conforming files, but what's a viable migration path for people that already have them? -- 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]
