Joffreybvn commented on PR #32319: URL: https://github.com/apache/airflow/pull/32319#issuecomment-1826875406
I'm whiling to create a new PR and pause/drop this one. But, during the implementation of this PR, I could not create/instantiate pyobc.Row objects ([which is a C++ object](https://github.com/mkleehammer/pyodbc/blob/master/src/row.cpp)) directly in Python. Thus I assumed it is not possible... *(but I never had this case, and maybe there's something to learn here !)* Quoting [you](https://github.com/apache/airflow/discussions/32058#discussioncomment-7673513): > 1. Add a serialize / deserialize method to the object > 2. Add a serializer/deserializer into airflow.serialization.serializers > 3. Decorate the object with @DataClass or @attr Assuming creating a deserializer which returns a pyodbc.Row object is not possible, is it okay to return a Namedtuple ? Isn't better to get rid of the C++ objects as early as possible, so that the user deal with NamedTuple all the way ? -- 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]
