zeroshade commented on issue #34292: URL: https://github.com/apache/arrow/issues/34292#issuecomment-1448564484
I can think of a couple ways to go about this. * Adding methods to the ExtensionType itself which can be used / define how to marshal/unmarshal the data itself (not just serializing and deserializing the type) * Accepting an optional Unmarshaller object when creating an extension builder and then having the builder determine whether to delegate to it if it exists or to delegate to the underlying storage builder if it isn't set. * Following the `ExtensionArray` method by making the ExtensionBuilder a "must-embed" type and an ExtensionBuilder interface that includes `UnmarshalJSON` along with adding a function to the extension type to return the type of the extension builder to use (like what is done for returning a `reflect.Type` for the ExtensionArray type) What do you think? -- 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]
