[jira] [Created] (AIRFLOW-3303) Deprecate old UI in favor of new FAB RBAC
Verdan Mahmood created AIRFLOW-3303: --- Summary: Deprecate old UI in favor of new FAB RBAC Key: AIRFLOW-3303 URL: https://issues.apache.org/jira/browse/AIRFLOW-3303 Project: Apache Airflow Issue Type: Improvement Components: ui Reporter: Verdan Mahmood Assignee: Verdan Mahmood It's hard to maintain two multiple UIs in parallel. The idea is to remove the old UI in favor of the new FAB RBAC version. Make sure to verify all the REST APIs are in place, and working. All test cases should pass. Skip the tests related to the old UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2874) Enable Flask App Builder theme support
[ https://issues.apache.org/jira/browse/AIRFLOW-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2874: Description: To customize the look and feel of Apache Airflow (an effort towards making Airflow a whitelabel application), we should enable the support of FAB's theme, which can be set in configuration. Theme can be use in conjunction of existing `navbar_color` configuration or can be used separately by simple unsetting the navbar_color config. http://flask-appbuilder.readthedocs.io/en/latest/customizing.html#changing-themes was: To customize the look and feel of Apache Airflow, we should enable the support of FAB's theme, which can be set in configuration. Theme can be use in conjunction of existing `navbar_color` configuration or can be used separately by simple unsetting the navbar_color config. > Enable Flask App Builder theme support > -- > > Key: AIRFLOW-2874 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2874 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > > To customize the look and feel of Apache Airflow (an effort towards making > Airflow a whitelabel application), we should enable the support of FAB's > theme, which can be set in configuration. > Theme can be use in conjunction of existing `navbar_color` configuration or > can be used separately by simple unsetting the navbar_color config. > > http://flask-appbuilder.readthedocs.io/en/latest/customizing.html#changing-themes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2874) Enable Flask App Builder theme support
Verdan Mahmood created AIRFLOW-2874: --- Summary: Enable Flask App Builder theme support Key: AIRFLOW-2874 URL: https://issues.apache.org/jira/browse/AIRFLOW-2874 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood Assignee: Verdan Mahmood To customize the look and feel of Apache Airflow, we should enable the support of FAB's theme, which can be set in configuration. Theme can be use in conjunction of existing `navbar_color` configuration or can be used separately by simple unsetting the navbar_color config. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2805: Attachment: Screen Shot 2018-08-02 at 1.08.53 PM.png > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 1.08.53 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2805: Attachment: (was: Screen Shot 2018-08-02 at 1.03.30 PM.png) > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 1.08.53 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566610#comment-16566610 ] Verdan Mahmood edited comment on AIRFLOW-2805 at 8/2/18 11:09 AM: -- [~cctvzd7] I mean to display the Start and End date of a process in different timezone. Not sure if we also should display the DAG Run time in different timezones. Something like this: !Screen Shot 2018-08-02 at 1.08.53 PM.png! was (Author: verdan): [~cctvzd7] I mean to display the Start and End date of a process in different timezone. Not sure if we also should display the DAG Run time in different timezones. Something like this: !Screen Shot 2018-08-02 at 1.03.30 PM.png! > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 1.08.53 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2805: Attachment: Screen Shot 2018-08-02 at 1.03.30 PM.png > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 1.03.30 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2805: Attachment: (was: Screen Shot 2018-08-02 at 12.42.01 PM.png) > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 1.03.30 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566610#comment-16566610 ] Verdan Mahmood commented on AIRFLOW-2805: - [~cctvzd7] I mean to display the Start and End date of a process in different timezone. Not sure if we also should display the DAG Run time in different timezones. Something like this: !Screen Shot 2018-08-02 at 12.42.01 PM.png! > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 12.42.01 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2805: Attachment: Screen Shot 2018-08-02 at 12.42.01 PM.png > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Attachments: Screen Shot 2018-08-02 at 12.42.01 PM.png > > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2803) Fix all ESLint issues
[ https://issues.apache.org/jira/browse/AIRFLOW-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561591#comment-16561591 ] Verdan Mahmood commented on AIRFLOW-2803: - [~tedmiston] thanks for picking this up. I'm using Node 8.11.3 and npm 6.1.0 > Fix all ESLint issues > - > > Key: AIRFLOW-2803 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2803 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Taylor Edmiston >Priority: Major > > Most of the JS code in Apache Airflow has linting issues which are > highlighted after the integration of ESLint. > Once AIRFLOW-2783 merged in master branch, please fix all the javascript > styling issues that we have in .js and .html files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2691) Make Airflow's JS code (and dependencies) manageable via npm and webpack
[ https://issues.apache.org/jira/browse/AIRFLOW-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561590#comment-16561590 ] Verdan Mahmood commented on AIRFLOW-2691: - nice catch [~kevcampb], I've added a new JIRA issue for this documentation, and will make sure to pick this up ASAP. ref: https://issues.apache.org/jira/browse/AIRFLOW-2823 > Make Airflow's JS code (and dependencies) manageable via npm and webpack > > > Key: AIRFLOW-2691 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2691 > Project: Apache Airflow > Issue Type: New Feature >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Fix For: 2.0.0 > > > Airflow's JS code is hard to maintain and upgrade. The dependencies are > locally existing files making it hard to upgrade versions. > Make sure Airflow uses *npm* and *webpack* for the dependencies management. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2823) Improve documentation of the new JS package manager installation
Verdan Mahmood created AIRFLOW-2823: --- Summary: Improve documentation of the new JS package manager installation Key: AIRFLOW-2823 URL: https://issues.apache.org/jira/browse/AIRFLOW-2823 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood Assignee: Verdan Mahmood With the implementation of npm and webpack for JS packages and dependencies (AIRFLOW-2691), please make sure to document that change for the users who don't simply use the distributed version of Apache Airflow and install that directly using the source code. The details about how to install and compile the JS packages can be added in INSTALL file on the root so that users can understand quickly how to install and compile the JS packages. Note: The information is already available in CONTRIBUTING.md file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AIRFLOW-2804) Extract inline JS from html files and move them in separate .js files
[ https://issues.apache.org/jira/browse/AIRFLOW-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood reassigned AIRFLOW-2804: --- Assignee: Verdan Mahmood > Extract inline JS from html files and move them in separate .js files > - > > Key: AIRFLOW-2804 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2804 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > > Apache Airflow uses inline JS code on most/all of the pages, making it > difficult to optimize/minimfy them properly. > Please make full use of npm and webpack by extracting all inline JS from html > files, moving them in separate .js files and make use of `require` and > `import` to optimize the dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
[ https://issues.apache.org/jira/browse/AIRFLOW-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood reassigned AIRFLOW-2805: --- Assignee: Verdan Mahmood > Display user's local timezone and DAG's timezone on UI > -- > > Key: AIRFLOW-2805 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > > The UI currently only displays the UTC timezone which is also not in human > readable forms on all places. > Make all the date times in human readable forms. > Also, we need to display user's local timezone and DAG's timezone along with > UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2803) Fix all ESLint issues
[ https://issues.apache.org/jira/browse/AIRFLOW-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559418#comment-16559418 ] Verdan Mahmood commented on AIRFLOW-2803: - [~tedmiston] I believe you'd be able to resolve most of them by running `npm run lint:fix` command. > Fix all ESLint issues > - > > Key: AIRFLOW-2803 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2803 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Taylor Edmiston >Priority: Major > > Most of the JS code in Apache Airflow has linting issues which are > highlighted after the integration of ESLint. > Once AIRFLOW-2783 merged in master branch, please fix all the javascript > styling issues that we have in .js and .html files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2805) Display user's local timezone and DAG's timezone on UI
Verdan Mahmood created AIRFLOW-2805: --- Summary: Display user's local timezone and DAG's timezone on UI Key: AIRFLOW-2805 URL: https://issues.apache.org/jira/browse/AIRFLOW-2805 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood The UI currently only displays the UTC timezone which is also not in human readable forms on all places. Make all the date times in human readable forms. Also, we need to display user's local timezone and DAG's timezone along with UTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2730) Airflow 1.9.0+ Web UI Fails to Load in IE11
[ https://issues.apache.org/jira/browse/AIRFLOW-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558150#comment-16558150 ] Verdan Mahmood commented on AIRFLOW-2730: - I believe it would make more sense to pick this issue after extracting all inline JS from html files into separate .js file. I've created a new JIRA issue to do that. https://issues.apache.org/jira/browse/AIRFLOW-2804 > Airflow 1.9.0+ Web UI Fails to Load in IE11 > --- > > Key: AIRFLOW-2730 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2730 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.9.0 >Reporter: Cameron Yick >Priority: Minor > > As a developer, I would like to use Airflow in enterprise environments where > IE11 is the only browser available. > Presently, the admin view doesn't load because some of the inlined javascript > on the page uses ES6 features, like the array spread operator. > Fixing this change will become a lot easier after AIRFLOW-2691 goes through, > because transpilation could happen as part of the build process. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2804) Extract inline JS from html files and move them in separate .js files
Verdan Mahmood created AIRFLOW-2804: --- Summary: Extract inline JS from html files and move them in separate .js files Key: AIRFLOW-2804 URL: https://issues.apache.org/jira/browse/AIRFLOW-2804 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood Apache Airflow uses inline JS code on most/all of the pages, making it difficult to optimize/minimfy them properly. Please make full use of npm and webpack by extracting all inline JS from html files, moving them in separate .js files and make use of `require` and `import` to optimize the dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2803) Fix all ESLint issues
Verdan Mahmood created AIRFLOW-2803: --- Summary: Fix all ESLint issues Key: AIRFLOW-2803 URL: https://issues.apache.org/jira/browse/AIRFLOW-2803 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood Most of the JS code in Apache Airflow has linting issues which are highlighted after the integration of ESLint. Once AIRFLOW-2783 merged in master branch, please fix all the javascript styling issues that we have in .js and .html files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2783) Integrate `eslint` with a decent set of rules
[ https://issues.apache.org/jira/browse/AIRFLOW-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2783: Description: To make sure that the javascript code is standardized and well written, we should integrate eslint with a decent set of rules, so that everyone follows those rules while writing the JS. https://eslint.org/ was:To make sure that the javascript code is standardized and well written, we should integrate eslint with a decent set of rules, so that everyone follows those rules while writing the JS. > Integrate `eslint` with a decent set of rules > - > > Key: AIRFLOW-2783 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2783 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Priority: Major > > To make sure that the javascript code is standardized and well written, we > should integrate eslint with a decent set of rules, so that everyone follows > those rules while writing the JS. > https://eslint.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2783) Integrate `eslint` with a decent set of rules
Verdan Mahmood created AIRFLOW-2783: --- Summary: Integrate `eslint` with a decent set of rules Key: AIRFLOW-2783 URL: https://issues.apache.org/jira/browse/AIRFLOW-2783 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood To make sure that the javascript code is standardized and well written, we should integrate eslint with a decent set of rules, so that everyone follows those rules while writing the JS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2782) Upgrade Dagre D3 version to latest possible
Verdan Mahmood created AIRFLOW-2782: --- Summary: Upgrade Dagre D3 version to latest possible Key: AIRFLOW-2782 URL: https://issues.apache.org/jira/browse/AIRFLOW-2782 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood Assignee: Verdan Mahmood The current version of DagreD3 we are using is really old and is not supported with new version of npm and webpack 4+, and the library is currently placed locally in the code-base and not managed via webpack. Please upgrade the DagreD3 to latest possible version so it can be managed through npm and webpack. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2766) Replicated *Base date* in each tab on DAG detail view
[ https://issues.apache.org/jira/browse/AIRFLOW-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2766: Description: At the moment, most of the tabs on DAG detail page has the *Base date* feature which behaves only for that particular tab/view. From end-user's perspective it is confusing as a user assume to select a date and then see all views based on that date The idea is to move the *Base date* outside the tabs, and each tab will then behave on the *Base date* on the Global level. Users will then only need to select the base date once and every tab will behave on that date. Please see attached screenshot for reference Or, the second approach could be to make sure the change of Base Date in each tab remains the same and doesn't change on page refresh. was: At the moment, most of the tabs on DAG detail page has the *Base date* feature which behaves only for that particular tab/view. From end-user's perspective it is confusing as a user assume to select a date and then see all views based on that date The idea is to move the *Base date* outside the tabs, and each tab will then behave on the *Base date* on the Global level. Users will then only need to select the base date once and every tab will behave on that date. Please see attached screenshot for reference Or, the second approach could be to make sure the change of Base Date in each tab remains the same and doesn't change on page refresh, and then move the DAG's meta data tabs (Details, Code, Refresh and Delete buttons) to the top, separating group of metadata and graphs. > Replicated *Base date* in each tab on DAG detail view > - > > Key: AIRFLOW-2766 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2766 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Minor > Attachments: Screen Shot 2018-07-18 at 1.57.22 PM.png > > > At the moment, most of the tabs on DAG detail page has the *Base date* > feature which behaves only for that particular tab/view. From end-user's > perspective it is confusing as a user assume to select a date and then see > all views based on that date > The idea is to move the *Base date* outside the tabs, and each tab will then > behave on the *Base date* on the Global level. Users will then only need to > select the base date once and every tab will behave on that date. > Please see attached screenshot for reference > Or, the second approach could be to make sure the change of Base Date in each > tab remains the same and doesn't change on page refresh. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2766) Replicated *Base date* in each tab on DAG detail view
[ https://issues.apache.org/jira/browse/AIRFLOW-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2766: Attachment: Screen Shot 2018-07-18 at 1.57.22 PM.png > Replicated *Base date* in each tab on DAG detail view > - > > Key: AIRFLOW-2766 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2766 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Minor > Attachments: Screen Shot 2018-07-18 at 1.57.22 PM.png > > > At the moment, most of the tabs on DAG detail page has the *Base date* > feature which behaves only for that particular tab/view. From end-user's > perspective it is confusing as a user assume to select a date and then see > all views based on that date > The idea is to move the *Base date* outside the tabs, and each tab will then > behave on the *Base date* on the Global level. Users will then only need to > select the base date once and every tab will behave on that date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2766) Replicated *Base date* in each tab on DAG detail view
Verdan Mahmood created AIRFLOW-2766: --- Summary: Replicated *Base date* in each tab on DAG detail view Key: AIRFLOW-2766 URL: https://issues.apache.org/jira/browse/AIRFLOW-2766 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood Assignee: Verdan Mahmood At the moment, most of the tabs on DAG detail page has the *Base date* feature which behaves only for that particular tab/view. From end-user's perspective it is confusing as a user assume to select a date and then see all views based on that date The idea is to move the *Base date* outside the tabs, and each tab will then behave on the *Base date* on the Global level. Users will then only need to select the base date once and every tab will behave on that date. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2764) Discription for dags
[ https://issues.apache.org/jira/browse/AIRFLOW-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547610#comment-16547610 ] Verdan Mahmood commented on AIRFLOW-2764: - [~jackjack10] the description/documentation is already visible in the detail UI (“Graph View” for dags, “Task Details” for tasks), and can serve the purpose you mentioned. Please correct me if I'm wrong. ref: https://airflow.apache.org/concepts.html#documentation-notes > Discription for dags > > > Key: AIRFLOW-2764 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2764 > Project: Apache Airflow > Issue Type: Wish >Reporter: jack >Priority: Minor > Fix For: Airflow 2.0 > > > Currently in the UI we see the dag_id of the DAG. > When many users use the UI it's not always clear what the DAG does. > It will be extremely helpful if in the UI we can see a short description of > the DAG. > Example: > Dag Description Schedule > Report this is the description 0 4 *** -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2691) Make Airflow's JS code (and dependencies) manageable via npm and webpack
[ https://issues.apache.org/jira/browse/AIRFLOW-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2691: Description: Airflow's JS code is hard to maintain and upgrade. The dependencies are locally existing files making it hard to upgrade versions. Make sure Airflow uses *npm* and *webpack* for the dependencies management. was: Airflow's JS code is hard to maintain and upgrade. The dependencies are locally existing files making it hard to upgrade versions. Make sure Airflow uses `npm` and `webpack` for the dependencies management. > Make Airflow's JS code (and dependencies) manageable via npm and webpack > > > Key: AIRFLOW-2691 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2691 > Project: Apache Airflow > Issue Type: New Feature >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > > Airflow's JS code is hard to maintain and upgrade. The dependencies are > locally existing files making it hard to upgrade versions. > Make sure Airflow uses *npm* and *webpack* for the dependencies management. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2691) Make Airflow's JS code (and dependencies) manageable via npm and webpack
Verdan Mahmood created AIRFLOW-2691: --- Summary: Make Airflow's JS code (and dependencies) manageable via npm and webpack Key: AIRFLOW-2691 URL: https://issues.apache.org/jira/browse/AIRFLOW-2691 Project: Apache Airflow Issue Type: New Feature Reporter: Verdan Mahmood Assignee: Verdan Mahmood Airflow's JS code is hard to maintain and upgrade. The dependencies are locally existing files making it hard to upgrade versions. Make sure Airflow uses `npm` and `webpack` for the dependencies management. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2667) Create an API that returns all configurations of Airflow
[ https://issues.apache.org/jira/browse/AIRFLOW-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2667: Description: Implement an API that will return all configurations from Airflow's config file. One can also pass a `?section=` query string parameter to get any particular section from configurations. was:Implement an API that will return all configurations from Airflow's config file. > Create an API that returns all configurations of Airflow > > > Key: AIRFLOW-2667 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2667 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: api, api-required > > Implement an API that will return all configurations from Airflow's config > file. > One can also pass a `?section=` query string parameter to get any particular > section from configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2667) Create an API that returns webserver configurations of Airflow
[ https://issues.apache.org/jira/browse/AIRFLOW-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2667: Description: Implement an API that will return all configurations from Airflow's config file. (was: Implement an API that will return webserver configurations from Airflow's config file. ) > Create an API that returns webserver configurations of Airflow > -- > > Key: AIRFLOW-2667 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2667 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: api, api-required > > Implement an API that will return all configurations from Airflow's config > file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2667) Create an API that returns all configurations of Airflow
[ https://issues.apache.org/jira/browse/AIRFLOW-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2667: Summary: Create an API that returns all configurations of Airflow (was: Create an API that returns webserver configurations of Airflow) > Create an API that returns all configurations of Airflow > > > Key: AIRFLOW-2667 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2667 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: api, api-required > > Implement an API that will return all configurations from Airflow's config > file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2667) Create an API that returns webserver configurations of Airflow
[ https://issues.apache.org/jira/browse/AIRFLOW-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2667: Summary: Create an API that returns webserver configurations of Airflow (was: Create an API that returns all configurations of Airflow) > Create an API that returns webserver configurations of Airflow > -- > > Key: AIRFLOW-2667 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2667 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: api, api-required > > Implement an API that will return all configurations from Airflow's config > file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2667) Create an API that returns webserver configurations of Airflow
[ https://issues.apache.org/jira/browse/AIRFLOW-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2667: Description: Implement an API that will return webserver configurations from Airflow's config file. (was: Implement an API that will return all configurations from Airflow's config file. ) > Create an API that returns webserver configurations of Airflow > -- > > Key: AIRFLOW-2667 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2667 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: api, api-required > > Implement an API that will return webserver configurations from Airflow's > config file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2667) Create an API that returns all configurations of Airflow
Verdan Mahmood created AIRFLOW-2667: --- Summary: Create an API that returns all configurations of Airflow Key: AIRFLOW-2667 URL: https://issues.apache.org/jira/browse/AIRFLOW-2667 Project: Apache Airflow Issue Type: New Feature Components: api Reporter: Verdan Mahmood Assignee: Verdan Mahmood Implement an API that will return all configurations from Airflow's config file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2628) A list of all APIs that we need in our system [WIP]
[ https://issues.apache.org/jira/browse/AIRFLOW-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2628: Description: *List of APIs needed* # /dags * ?owner= * ?last_run= * ?is_paused= * ?is_active= * ?schedule= * ?last_run= * ?is_subdag= # /dags/ [GET] (The details of a DAG) # /dags/ [PUT] (The details of a DAG) * is_paused * is_active * owners ? # /dags//code # /dags//dagruns/ [POST](Create a new DagRun / Trigger Dagrun) # /dags//dagruns/ [GET](Get all Dag Runs) * ?state= * ?external_trigger= # /dags//dagruns/ # /dags//dagruns/task_instances/ [POST] (Trigger a new instance) # /dags//dagruns/task_instances/ [GET] (Get all Task Instances of a DAG) # /dags//dagruns/task_instances/ # /dags//tasks [GET] (list of all tasks of a DAG) # /dags//tasks/ # /dags/dagruns/ * ?dag_id= * ?state= * ?execution_date= * ?external_trigger= * ?run_id= # /dags/dagruns/ # /dags/taskinstances/ * ?state= * ?dag_id= * ?task_id= * ?execution_date= * ?hostname= * ?queue= * ?pool= * ?operator= * ?start_date= * ?end_date= # /dags/taskinstances/ # /pools/ [GET|POST] # /pools/ [GET|PUT|DELETE] # /configuration # /connections/ [GET|POST] # /connections/ [GET|PUT|DELETE] # /variables/ [GET|POST] # /variables/ [GET|PUT|DELETE] # /variables/import [POST] (import variables from file) # /xcoms/ [GET|POST] # /xcoms/ [GET|PUT|DELETE] # /jobs/ was: *List of APIs needed* # /dags * ?owner= * ?last_run= * ?is_paused= * ?is_active= * ?schedule= * ?last_run= * ?is_subdag= # /dags/ [GET] (The details of a DAG) # /dags/ [PUT] (The details of a DAG) * is_paused * is_active * owners ? # /dags//code # /dags//dagruns/ [POST](Create a new DagRun / Trigger Dagrun) # /dags//dagruns/ [GET](Get all Dag Runs) * ?state= * ?external_trigger= # /dags//dagruns/ # /dags//dagruns/task_instances/ [POST] (Trigger a new instance) # /dags//dagruns/task_instances/ [GET] (Get all Task Instances of a DAG) # /dags//dagruns/task_instances/ # /dags//tasks [GET] (list of all tasks of a DAG) # /dags//tasks/ # /dags/dagruns/ * ?dag_id= * ?state= * ?execution_date= * ?external_trigger= * ?run_id= # /dags/dagruns/ # /dags/taskinstances/ * ?state= * ?dag_id= * ?task_id= * ?execution_date= * ?hostname= * ?queue= * ?pool= * ?operator= * ?start_date= * ?end_date= # /dags/taskinstances/ # /pools/ [GET|POST] # /pools/ [GET|PUT|DELETE] # /configuration # /connections/ [GET|POST] # /connections/ [GET|PUT|DELETE] # /variables/ [GET|POST] # /variables/ [GET|PUT|DELETE] # /variables/import [POST] (import variables from file) # /xcoms/ [GET|POST] # /xcoms/ [GET|PUT|DELETE] # /jobs/ > A list of all APIs that we need in our system [WIP] > --- > > Key: AIRFLOW-2628 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2628 > Project: Apache Airflow > Issue Type: Task > Components: api >Reporter: Verdan Mahmood >Priority: Trivial > > *List of APIs needed* > > # /dags > * ?owner= > * ?last_run= > * ?is_paused= > * ?is_active= > * ?schedule= > * ?last_run= > * ?is_subdag= > # /dags/ [GET] (The details of a DAG) > # /dags/ [PUT] (The details of a DAG) > * is_paused > * is_active > * owners ? > # /dags//code > # /dags//dagruns/ [POST](Create a new DagRun / Trigger Dagrun) > # /dags//dagruns/ [GET](Get all Dag Runs) > * ?state= > * ?external_trigger= > # /dags//dagruns/ > # /dags//dagruns/task_instances/ [POST] (Trigger a new instance) > # /dags//dagruns/task_instances/ [GET] (Get all Task Instances of a > DAG) > # /dags//dagruns/task_instances/ > # /dags//tasks [GET] (list of all tasks of a DAG) > # /dags//tasks/ > # /dags/dagruns/ > * ?dag_id= > * ?state= > * ?execution_date= > * ?external_trigger= > * ?run_id= > # /dags/dagruns/ > # /dags/taskinstances/ > * ?state= > * ?dag_id= > * ?task_id= > * ?execution_date= > * ?hostname= > * ?queue= > * ?pool= > * ?operator= > * ?start_date= > * ?end_date= > # /dags/taskinstances/ > # /pools/ [GET|POST] > # /pools/ [GET|PUT|DELETE] > # /configuration > # /connections/ [GET|POST] > # /connections/ [GET|PUT|DELETE] > # /variables/ [GET|POST] > # /variables/ [GET|PUT|DELETE] > # /variables/import [POST] (import variables from file) > # /xcoms/ [GET|POST] > # /xcoms/ [GET|PUT|DELETE] > # /jobs/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2628) A list of all APIs that we need in our system [WIP]
Verdan Mahmood created AIRFLOW-2628: --- Summary: A list of all APIs that we need in our system [WIP] Key: AIRFLOW-2628 URL: https://issues.apache.org/jira/browse/AIRFLOW-2628 Project: Apache Airflow Issue Type: Task Components: api Reporter: Verdan Mahmood *List of APIs needed* # /dags * ?owner= * ?last_run= * ?is_paused= * ?is_active= * ?schedule= * ?last_run= * ?is_subdag= # /dags/ [GET] (The details of a DAG) # /dags/ [PUT] (The details of a DAG) * is_paused * is_active * owners ? # /dags//code # /dags//dagruns/ [POST](Create a new DagRun / Trigger Dagrun) # /dags//dagruns/ [GET](Get all Dag Runs) * ?state= * ?external_trigger= # /dags//dagruns/ # /dags//dagruns/task_instances/ [POST] (Trigger a new instance) # /dags//dagruns/task_instances/ [GET] (Get all Task Instances of a DAG) # /dags//dagruns/task_instances/ # /dags//tasks [GET] (list of all tasks of a DAG) # /dags//tasks/ # /dags/dagruns/ * ?dag_id= * ?state= * ?execution_date= * ?external_trigger= * ?run_id= # /dags/dagruns/ # /dags/taskinstances/ * ?state= * ?dag_id= * ?task_id= * ?execution_date= * ?hostname= * ?queue= * ?pool= * ?operator= * ?start_date= * ?end_date= # /dags/taskinstances/ # /pools/ [GET|POST] # /pools/ [GET|PUT|DELETE] # /configuration # /connections/ [GET|POST] # /connections/ [GET|PUT|DELETE] # /variables/ [GET|POST] # /variables/ [GET|PUT|DELETE] # /variables/import [POST] (import variables from file) # /xcoms/ [GET|POST] # /xcoms/ [GET|PUT|DELETE] # /jobs/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2550) API endpoint to list dagruns
[ https://issues.apache.org/jira/browse/AIRFLOW-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16513509#comment-16513509 ] Verdan Mahmood commented on AIRFLOW-2550: - that's good to know [~rcorre] :) I am working on adding/completing the APIs for the Airflow so that I can rewrite the whole frontend in ReactJS. ref: https://issues.apache.org/jira/browse/AIRFLOW-2598 so perhaps once you have your approval, you'll be able to contribute more towards it? In the meantime can you please review my PR? > API endpoint to list dagruns > > > Key: AIRFLOW-2550 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2550 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Ryan Roden-Corrent >Assignee: Verdan Mahmood >Priority: Major > > There should be an endpoint, say 'GET /dags//dag_runs` that > lists all runs for a given DAG. > > Related: https://issues.apache.org/jira/browse/AIRFLOW-1919 is requesting a > similar CLI option, though in our case we need all runs, not just actively > running runs. Possibly a ?state=running query option could be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2625) Create an API to list all the available DAGs
Verdan Mahmood created AIRFLOW-2625: --- Summary: Create an API to list all the available DAGs Key: AIRFLOW-2625 URL: https://issues.apache.org/jira/browse/AIRFLOW-2625 Project: Apache Airflow Issue Type: New Feature Components: api, DAG Reporter: Verdan Mahmood There should be an API to list all the available DAGs in the system. (this is basically same as the DAGs list page aka Airflow home page) This should include all the basic information related to a DAG. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2607) test_trigger_dag need to be fixed
[ https://issues.apache.org/jira/browse/AIRFLOW-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512399#comment-16512399 ] Verdan Mahmood commented on AIRFLOW-2607: - https://github.com/apache/incubator-airflow/pull/3494 > test_trigger_dag need to be fixed > - > > Key: AIRFLOW-2607 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2607 > Project: Apache Airflow > Issue Type: Bug > Components: api, tests >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: test-fail > > test_trigger_dag is failing, and need to be fixed. (used docker with python3 > environment for testing) > File: tests/api/client/test_local_client.py > Class: TestLocalClient > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (AIRFLOW-2608) Improved Exceptions handling in APIs
[ https://issues.apache.org/jira/browse/AIRFLOW-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AIRFLOW-2608 started by Verdan Mahmood. --- > Improved Exceptions handling in APIs > > > Key: AIRFLOW-2608 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2608 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: exception-handling > > The error handling in APIs is very poor, and most of the exceptions are > raised directly from AirflowExceptions which is the base exceptions class. > Also, some of the custom exceptions are created locally under the scope of > each file making it duplicated for other files. > We should have a centralized location for Exception classes along with the > standard default message for each exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2608) Improved Exceptions handling in APIs
[ https://issues.apache.org/jira/browse/AIRFLOW-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512396#comment-16512396 ] Verdan Mahmood commented on AIRFLOW-2608: - https://github.com/apache/incubator-airflow/pull/3496 > Improved Exceptions handling in APIs > > > Key: AIRFLOW-2608 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2608 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: exception-handling > > The error handling in APIs is very poor, and most of the exceptions are > raised directly from AirflowExceptions which is the base exceptions class. > Also, some of the custom exceptions are created locally under the scope of > each file making it duplicated for other files. > We should have a centralized location for Exception classes along with the > standard default message for each exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (AIRFLOW-2607) test_trigger_dag need to be fixed
[ https://issues.apache.org/jira/browse/AIRFLOW-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AIRFLOW-2607 started by Verdan Mahmood. --- > test_trigger_dag need to be fixed > - > > Key: AIRFLOW-2607 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2607 > Project: Apache Airflow > Issue Type: Bug > Components: api, tests >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: test-fail > > test_trigger_dag is failing, and need to be fixed. (used docker with python3 > environment for testing) > File: tests/api/client/test_local_client.py > Class: TestLocalClient > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2550) API endpoint to list dagruns
[ https://issues.apache.org/jira/browse/AIRFLOW-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512387#comment-16512387 ] Verdan Mahmood commented on AIRFLOW-2550: - https://github.com/apache/incubator-airflow/pull/3499 > API endpoint to list dagruns > > > Key: AIRFLOW-2550 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2550 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Ryan Roden-Corrent >Assignee: Verdan Mahmood >Priority: Major > > There should be an endpoint, say 'GET /dags//dag_runs` that > lists all runs for a given DAG. > > Related: https://issues.apache.org/jira/browse/AIRFLOW-1919 is requesting a > similar CLI option, though in our case we need all runs, not just actively > running runs. Possibly a ?state=running query option could be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AIRFLOW-2550) API endpoint to list dagruns
[ https://issues.apache.org/jira/browse/AIRFLOW-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood reassigned AIRFLOW-2550: --- Assignee: Verdan Mahmood > API endpoint to list dagruns > > > Key: AIRFLOW-2550 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2550 > Project: Apache Airflow > Issue Type: New Feature > Components: api >Reporter: Ryan Roden-Corrent >Assignee: Verdan Mahmood >Priority: Major > > There should be an endpoint, say 'GET /dags//dag_runs` that > lists all runs for a given DAG. > > Related: https://issues.apache.org/jira/browse/AIRFLOW-1919 is requesting a > similar CLI option, though in our case we need all runs, not just actively > running runs. Possibly a ?state=running query option could be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2616) Pluggable class-based views for APIs
Verdan Mahmood created AIRFLOW-2616: --- Summary: Pluggable class-based views for APIs Key: AIRFLOW-2616 URL: https://issues.apache.org/jira/browse/AIRFLOW-2616 Project: Apache Airflow Issue Type: Improvement Components: api Reporter: Verdan Mahmood With the increase of API code base, the current architecture (functional views) will become messy in no time. Same routes with different http methods become more confusing in the code base. We can either use Flask's Pluggable views, which are inspired by Django's generic class-based views to make our API structure more modular, or we can look for Flask-RESTful framework. http://flask.pocoo.org/docs/0.12/views/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AIRFLOW-2607) test_trigger_dag need to be fixed
[ https://issues.apache.org/jira/browse/AIRFLOW-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood reassigned AIRFLOW-2607: --- Assignee: Verdan Mahmood > test_trigger_dag need to be fixed > - > > Key: AIRFLOW-2607 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2607 > Project: Apache Airflow > Issue Type: Bug > Components: api, tests >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: test-fail > > test_trigger_dag is failing, and need to be fixed. (used docker with python3 > environment for testing) > File: tests/api/client/test_local_client.py > Class: TestLocalClient > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AIRFLOW-2608) Improved Exceptions handling in APIs
[ https://issues.apache.org/jira/browse/AIRFLOW-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood reassigned AIRFLOW-2608: --- Assignee: Verdan Mahmood > Improved Exceptions handling in APIs > > > Key: AIRFLOW-2608 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2608 > Project: Apache Airflow > Issue Type: Improvement >Reporter: Verdan Mahmood >Assignee: Verdan Mahmood >Priority: Major > Labels: exception-handling > > The error handling in APIs is very poor, and most of the exceptions are > raised directly from AirflowExceptions which is the base exceptions class. > Also, some of the custom exceptions are created locally under the scope of > each file making it duplicated for other files. > We should have a centralized location for Exception classes along with the > standard default message for each exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2608) Improved Exceptions handling in APIs
Verdan Mahmood created AIRFLOW-2608: --- Summary: Improved Exceptions handling in APIs Key: AIRFLOW-2608 URL: https://issues.apache.org/jira/browse/AIRFLOW-2608 Project: Apache Airflow Issue Type: Improvement Reporter: Verdan Mahmood The error handling in APIs is very poor, and most of the exceptions are raised directly from AirflowExceptions which is the base exceptions class. Also, some of the custom exceptions are created locally under the scope of each file making it duplicated for other files. We should have a centralized location for Exception classes along with the standard default message for each exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRFLOW-2607) test_trigger_dag need to be fixed
[ https://issues.apache.org/jira/browse/AIRFLOW-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Verdan Mahmood updated AIRFLOW-2607: Description: test_trigger_dag is failing, and need to be fixed. (used docker with python3 environment for testing) File: tests/api/client/test_local_client.py Class: TestLocalClient was: test_trigger_dag is failing, and need to be fixed. File: tests/api/client/test_local_client.py Class: TestLocalClient > test_trigger_dag need to be fixed > - > > Key: AIRFLOW-2607 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2607 > Project: Apache Airflow > Issue Type: Bug > Components: api, tests >Reporter: Verdan Mahmood >Priority: Major > Labels: test-fail > > test_trigger_dag is failing, and need to be fixed. (used docker with python3 > environment for testing) > File: tests/api/client/test_local_client.py > Class: TestLocalClient > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2607) test_trigger_dag need to be fixed
Verdan Mahmood created AIRFLOW-2607: --- Summary: test_trigger_dag need to be fixed Key: AIRFLOW-2607 URL: https://issues.apache.org/jira/browse/AIRFLOW-2607 Project: Apache Airflow Issue Type: Bug Components: api, tests Reporter: Verdan Mahmood test_trigger_dag is failing, and need to be fixed. File: tests/api/client/test_local_client.py Class: TestLocalClient -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AIRFLOW-2598) Migrate Airflow to ReactJS
[ https://issues.apache.org/jira/browse/AIRFLOW-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509450#comment-16509450 ] Verdan Mahmood edited comment on AIRFLOW-2598 at 6/12/18 10:00 AM: --- Facebook actually removed all the BSD + Patent-licensed code from ReactJS last year with the launch of React 16. (which was the reason ASF took the drastic step of banning the library) React is now MIT licensed. ref: [https://github.com/facebook/react/blob/master/LICENSE] was (Author: verdan): Facebook actually removed all the BSD + Patent-licensed code from ReactJS (which was the reason ASF took the drastic step of banning the library) last year with the launch of React 16. React is now MIT licensed. ref: https://github.com/facebook/react/blob/master/LICENSE > Migrate Airflow to ReactJS > -- > > Key: AIRFLOW-2598 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2598 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp >Reporter: Verdan Mahmood >Priority: Major > Labels: frontend > > Hi guys, > In an effort to make the frontend of Apache Airflow more interactive and > feature-rich, I am planning to migrate the frontend to ReactJS. > The whole idea involves adding/updating the backend APIs and redesigning the > frontend in ReactJS, along with fixing bugs and improving layouts. This issue > is the starting point to discuss the need, process and timeline to make it > happen collectively. > For the next couple of weeks I would be working on backend in order to add > remaining APIs and make them ready for the frontend use. Question: Do we have > any kind of documentation or list of existing and outstanding APIs (roadmap)? > I am hoping to get your input on how to structure the frontend code, so that > we can deliver more frequently and incrementally in the best possible way. It > could be a separate repository or a directory within the same repository. > Thoughts? It would be great if I can also get some feedback on UI/UX, as > whether to keep it same or do some user research to improve that? > Note: I'll make sure to keep the backward compatibility in mind all the time > while doing that :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRFLOW-2598) Migrate Airflow to ReactJS
[ https://issues.apache.org/jira/browse/AIRFLOW-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509450#comment-16509450 ] Verdan Mahmood commented on AIRFLOW-2598: - Facebook actually removed all the BSD + Patent-licensed code from ReactJS (which was the reason ASF took the drastic step of banning the library) last year with the launch of React 16. React is now MIT licensed. ref: https://github.com/facebook/react/blob/master/LICENSE > Migrate Airflow to ReactJS > -- > > Key: AIRFLOW-2598 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2598 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp >Reporter: Verdan Mahmood >Priority: Major > Labels: frontend > > Hi guys, > In an effort to make the frontend of Apache Airflow more interactive and > feature-rich, I am planning to migrate the frontend to ReactJS. > The whole idea involves adding/updating the backend APIs and redesigning the > frontend in ReactJS, along with fixing bugs and improving layouts. This issue > is the starting point to discuss the need, process and timeline to make it > happen collectively. > For the next couple of weeks I would be working on backend in order to add > remaining APIs and make them ready for the frontend use. Question: Do we have > any kind of documentation or list of existing and outstanding APIs (roadmap)? > I am hoping to get your input on how to structure the frontend code, so that > we can deliver more frequently and incrementally in the best possible way. It > could be a separate repository or a directory within the same repository. > Thoughts? It would be great if I can also get some feedback on UI/UX, as > whether to keep it same or do some user research to improve that? > Note: I'll make sure to keep the backward compatibility in mind all the time > while doing that :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-2598) Migrate Airflow to ReactJS
Verdan Mahmood created AIRFLOW-2598: --- Summary: Migrate Airflow to ReactJS Key: AIRFLOW-2598 URL: https://issues.apache.org/jira/browse/AIRFLOW-2598 Project: Apache Airflow Issue Type: Improvement Components: webapp Reporter: Verdan Mahmood Hi guys, In an effort to make the frontend of Apache Airflow more interactive and feature-rich, I am planning to migrate the frontend to ReactJS. The whole idea involves adding/updating the backend APIs and redesigning the frontend in ReactJS, along with fixing bugs and improving layouts. This issue is the starting point to discuss the need, process and timeline to make it happen collectively. For the next couple of weeks I would be working on backend in order to add remaining APIs and make them ready for the frontend use. Question: Do we have any kind of documentation or list of existing and outstanding APIs (roadmap)? I am hoping to get your input on how to structure the frontend code, so that we can deliver more frequently and incrementally in the best possible way. It could be a separate repository or a directory within the same repository. Thoughts? It would be great if I can also get some feedback on UI/UX, as whether to keep it same or do some user research to improve that? Note: I'll make sure to keep the backward compatibility in mind all the time while doing that :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
