You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/03/11 16:41:06 UTC

[GitHub] [arrow-julia] jrevels commented on issue #303: Question on `Date` encoding

jrevels commented on issue #303:
URL: https://github.com/apache/arrow-julia/issues/303#issuecomment-1065286391


   (paraphrasing my response from Julia Slack)
   
   I guess either the Julia implementation could be considered "overly aggressive" as a producer here by other Arrow consumers since it encodes an extension for such a simple Julia type that maps 1:1 with an Arrow type. Alternatively, the consumer in this case may be considered "overly aggressive" in its attempt to resolve an extension that it's unaware of. Or maybe both 😁 
   
   IMO the latter interpretation (that the consumer should loosen its assumptions) probably makes more sense, unless there's guidance otherwise from core Arrow on how implementations should negotiate extension/metadata usage? A motivating example: if a producer writes out a column of structs and includes extension metadata to map the struct back into some application-layer type, I'd still want my extension-agnostic consumer to read the data as a column of "plain structs" gracefully instead of fail.
   
   (it's worth checking that the Julia implementation here doesn't suffer from the same problem - e.g. gracefully consumes Arrow data with unknown extensions. that'd be a different issue though)


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org