[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072166#comment-17072166
]
ASF subversion and git services commented on AIRFLOW-5590:
--
Commit 11eb53938359c6f27e5a9c59e9dc8223d62d in airflow's branch
refs/heads/v1-10-test from Kumpan Anton
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=11eb539 ]
[AIRFLOW-5590] Add run_id to trigger DAG run API response (#6256)
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
> Fix For: 1.10.10
>
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071987#comment-17071987
]
ASF subversion and git services commented on AIRFLOW-5590:
--
Commit e840ce8242a80e5e80caf88e00cc597d738bfbb5 in airflow's branch
refs/heads/v1-10-test from Kumpan Anton
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=e840ce8 ]
[AIRFLOW-5590] Add run_id to trigger DAG run API response (#6256)
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
> Fix For: 1.10.10
>
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071347#comment-17071347
]
ASF subversion and git services commented on AIRFLOW-5590:
--
Commit ebd11a2ab336681e4a1bce823de522f861e02a30 in airflow's branch
refs/heads/v1-10-test from Kumpan Anton
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=ebd11a2 ]
[AIRFLOW-5590] Add run_id to trigger DAG run API response (#6256)
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
> Fix For: 1.10.10
>
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035793#comment-17035793
]
ASF subversion and git services commented on AIRFLOW-5590:
--
Commit 96176273a86b8c35a003944265f18906501d1244 in airflow's branch
refs/heads/master from Kumpan Anton
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=9617627 ]
[AIRFLOW-5590] Add run_id to trigger DAG run API response (#6256)
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
> Fix For: 1.10.10
>
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035790#comment-17035790
]
ASF GitHub Bot commented on AIRFLOW-5590:
-
ashb commented on pull request #6256: [AIRFLOW-5590] Add run_id to trigger DAG
run API response
URL: https://github.com/apache/airflow/pull/6256
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:
us...@infra.apache.org
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17005116#comment-17005116
]
ASF GitHub Bot commented on AIRFLOW-5590:
-
stale[bot] commented on pull request #6514: AIRFLOW-5590: Add dagrun_id to the
response of experimental API on trigger.
URL: https://github.com/apache/airflow/pull/6514
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:
us...@infra.apache.org
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968724#comment-16968724
]
ASF GitHub Bot commented on AIRFLOW-5590:
-
douglasmakey commented on pull request #6514: AIRFLOW-5590: Add dagrun_id to
the response of experimental API on trigger.
URL: https://github.com/apache/airflow/pull/6514
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
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:
us...@infra.apache.org
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API response as a field
[
https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944147#comment-16944147
]
ASF GitHub Bot commented on AIRFLOW-5590:
-
aKumpan commented on pull request #6256: [AIRFLOW-5590] Add run_id to trigger
DAG run API response
URL: https://github.com/apache/airflow/pull/6256
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW-5590/) issues and
references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
I suggest to utilize 'run_id' instead of 'execution_date' as dag_runs unique
identifier for Rest APIs
[Proposal](https://issues.apache.org/jira/browse/AIRFLOW-5593). As a
pre-condition for this story - I am adding returning of **'run_id'** as a
separate parameter in json response.
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Updated existing tests
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
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:
us...@infra.apache.org
> Add 'run_id' to trigger DAG run API response as a field
> ---
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
>Affects Versions: 1.10.5
>Reporter: Anton Kumpan
>Assignee: Anton Kumpan
>Priority: Major
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will
> look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
