Hi, I asked earlier about supporting a scaled integer type to support point cloud data. I think a non-intrusive way to handle this would be to add an *optional* KeyValue member for metadata to the SchemaElement struct. This would take care of my needs and perhaps needs of others (someone wanted a "description" field). AFAICT this would require no changes on the part of any reader or writer -- only the file "parquet.thrift" file would need to be changed. This would provide readers and writers the *option* to access SchemaElement metadata, but there would be no requirement to do so.
I'm interested in feedback on this proposal. Thanks, -- Andrew Bell [email protected]
