You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bence Nagy (JIRA)" <ji...@apache.org> on 2016/07/04 09:02:11 UTC
[jira] [Created] (AIRFLOW-310) First class support for JSON
variables
Bence Nagy created AIRFLOW-310:
----------------------------------
Summary: First class support for JSON variables
Key: AIRFLOW-310
URL: https://issues.apache.org/jira/browse/AIRFLOW-310
Project: Apache Airflow
Issue Type: Wish
Reporter: Bence Nagy
Looking at our variables, every single one of them is JSON, the largest being 100 lines long. I will assume that most other users are mainly using JSON vars as well.
I can think of a few quality of life changes that could be made to make working with these variables easier:
- Make the 'Val' field on {{/admin/variable/edit}} use a fixed width font. This would probably not hurt non-JSON users either.
- Add JSON syntax highlighting to the textarea there.
- Add optional JSON syntax validation; perhaps a boolean flag in the DB for whether the var is supposed to be JSON. If true, reject non-valid updates to the variable, and perhaps don't require {{deserialize_json=True}} to be specified in the code every time it's accessed.
- This last one might be a bit far-fetched, but: Make it possible to add a [JSON schema file|http://json-schema.org/] that will be validated against on updates.
Let me know if you want these split into separate JIRA issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)