chaokunyang commented on issue #2160: URL: https://github.com/apache/fury/issues/2160#issuecomment-2835702100
> [@chaokunyang](https://github.com/chaokunyang) Hi, I just read through the specification document and have some questions to ask: > > 1. `meta_share` is used when a Fury object processes some objects of the same class multiple times. So if I use a Fury object sometimes deal with the parent class and sometimes the subclass, does that mean I shouldn't use meta_share? Are there any other situations where I need to be compatible but should not use meta_share? > 2. Is `schema evolution` the implementation approach of "type forward/backward compatibility"? > 3. Does this issue involve `codegen`? > > Thank you! Hi @urlyy , for your quesiont: 1. If you use Fury to deal with the parent class, fury need to write meta for parent class. If you use Fury to deal with the subclass, fury will write meta for subclass, but note that meta for subclass includes meta for parent class 2. You are right, `schema evolution spec` is the the implementation approach of "type forward/backward compatibility" 3. This issue doesn't involve `codegen`,, we should implement codegen in another PR. Currently we don't implement codegen for xlang serialization in python. Codegen will be supported after we merge ComplexObjectSerializer and DataclassSerializer into one serializer. -- 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]
