On Thu, 30 May 2024 00:07:35 -0700 Micah Kornfield <emkornfi...@gmail.com> wrote: > > A "vendor" encoding would also allow candidate encodings to be shared > > accross the ecosystem before they are eventually enchristened as regular > > encodings in the Thrift metadata. > > > I'm not a huge fan of this for two reasons: > 1. I think it makes it much more complicated for end-users to get support > if they happen to have a file with a custom encoding. There are already > enough rough edges in compatibility between implementations that this gives > another degree of freedom where things could break.
Agreed, but how is this not a problem for "pluggable" encodings as well? > 2. From a software supply chain perspective I think this makes Parquet a > lot riskier if it is going to arbitrarily load/invoke code from potentially > unknown sources. I'm not sure where that idea comes from. I did *not* suggest that implementations load arbitrary code from third-party Github repositories :-) Regards Antoine.
