Re: [I] Move XCom serialization and deserialization methods to the Task SDK [airflow]

["amoghrajesh (via GitHub)" <gi...@apache.org>]

amoghrajesh commented on issue #45231:
URL: https://github.com/apache/airflow/issues/45231#issuecomment-2656884316

   Latest update on this issue:
   
   - After discussion with @ashb, we arrived at a conclusion that the JSON is a globally accepted protocol which should be accepted across various languages, frameworks etc.
   - Due to this, we can enable our execution API server and in fact make it simpler to interact with.
   - To do this, we let the execution API server deal with JSON compliant types (json values like dict, list, str, int etc), and not json strings which would not make it too easy to interact with. For example:
   
   The new API response for get xcom now looks like:
   ```
   {
       "key": "return_value",
       "value": {
           "Hello": "XCom2!"
       }
   }
   ```
   
   contrary to:
   ```
   {
       "key": "return_value",
       "value": "{\"Hello\": \"XCom2!\"}"
   }
   
   ```
   
   - If the client wants to handle special encoding for any of the non json compliant types (custom defined or native to a language), those have to be handled in the client itself.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org