potiuk commented on issue #54781: URL: https://github.com/apache/airflow/issues/54781#issuecomment-3210936317
I think we have two ways of solving it: 1) More generic -> possibly we could serialize those classes (they are protobufs really) using generic to/from String and store the "class" of the object (so that we can deserialize it and know what to deserialize it from) 2) More "extendable" We could implement extendable serialization - and have providers to implement "serialize/deserialize" extention. We could have that Google-provider serialzation "extension" recognize and serialize/deserialize the objects we want. I am torn between the two. 1) is more generic but 2) is something I would also like to see for other providers possibly, and we could have a mechanism that finally allows to add serialization capabilities (and code) independently from airflow-core. WDYT. @kaxil @amoghrajesh @bolkedebruin @ashb ? -- 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]
