rok commented on PR #635: URL: https://github.com/apache/parquet-format/pull/635#issuecomment-6656578659
> I don't know... My hope was that inline would serve as a cache for small data for sequential read use cases. I was still hoping that we could still send the file reference to a remote server for example where it can read files directly instead of having to send the bytes over the wire. This change would force us to send the bytes over the wire. That's why we kept the definition somewhat open. Sending `uri`s over network instead ob `inline` bytes makes sense. As mutability of remote files is out of our scope we can't really prescribe anything about writing. But we do have etag and we can say that a reader can read either `inline` or `uri`, but if it chooses `uri` it should verify it with `etag`. -- 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]
