You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/02/14 15:11:03 UTC

[GitHub] [airflow] jonasrla edited a comment on issue #13934: EMR URI Parse Fails to resolve nested dict objects

jonasrla edited a comment on issue #13934:
URL: https://github.com/apache/airflow/issues/13934#issuecomment-778790585


   Hey guys,
   
   I'm considering now which way should we encode our nested objects.
   
   So looked up online and this issue and found [this discussion in angular project](https://github.com/angular/angular/issues/24868#issuecomment-409667751)
   
   So I suggest noting our nested object like
   
   ```
   {
     'extra1': {
       'nested_extra1': 'a value'
     },
     'extra2': 'other value'
   }
   ```
   as
   `extra1%5Bnested_extra1%5D=a%20value&extra2=other%20value`
   
   Extreme cases like
   ```
   {
     "a":
       {"b": "1",
        "c": {"d": "2"}
       },
     "e": "3"
   }
   ```
   would look like `a%5Bb%5D=1&a%5Bc%5D%5Bd%5D=2&e=3`
   
   And that does happen with AWS EMR connections. Checkout this [request form](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/emr.html#EMR.Client.run_job_flow)
   
   So any thoughts? Do you believe this way works?
   @vikramkoka, @mik-laj 


----------------------------------------------------------------
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.

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