DrChainsaw opened a new issue, #449: URL: https://github.com/apache/arrow-julia/issues/449
The current implementation seems to use the metadata tag `"ARROW:extension:name"` for julia specific types (e.g Symbols). Shouldn't this instead be something like `"ARROW:extension:arrow-julia.Symbol"` to make collisions less likely? Maybe I misunderstand the [extension documentation](https://arrow.apache.org/docs/format/Columnar.html#custom-application-metadata), but to me it seems like the tag `name` (and maybe also `extension`, docs are not super clear imo) is an example placeholder to be replaced with the actual name. With the above change it would be possible to write tables from other languages which make use of custom types in more than one language. For example, I'm writing tables from the java implementation and in many cases I would like strings to be deserialized as symbols (e.g. for enums), but that non-specific tag might block similar optimizations for other implementations. I guess it is not fun to change it due to backwards compatibility (probably need to support both tags for the forseeable future), but maybe better to rip of the bandaid as quickly as possible should it turn out that it should use a more specific tag. -- 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]
