[
https://issues.apache.org/jira/browse/OOZIE-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545838#comment-16545838
]
Thai Bui commented on OOZIE-3283:
---------------------------------
Holla folks, I just got sometime again and back to the ticket today and the
workflow listing prototype is complete! What's changed since the last update?
* Added Redux store and its dependency
* Added Redux-thunk dependency for async state changes from Oozie REST API
backend to the store
* Added Axios library for AJAX calls using Promise
* Handled table pagination, auto-refreshing the data from the Redux store
* Added reducers, actions and various mappings to connect/dispatch actions to
the store, the backend and the user's interactions
At this point, I think I'm pretty happy with everything. The only thing that
bothers me is the lack of CORS support in Oozie REST API. It is not easy to
start a local oozie process to test the frontend as well (I don't want to setup
HDFS, YARN, OOZIE just to test the frontend app). Currently, I'm using NGIX to
reverse-proxy to a qa/production cluster at my company to test the UI. It works
and is simpler that way.
> Prototyping: create React workflow list page
> --------------------------------------------
>
> Key: OOZIE-3283
> URL: https://issues.apache.org/jira/browse/OOZIE-3283
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Andras Piros
> Assignee: Thai Bui
> Priority: Major
> Attachments: Screen Shot 2018-06-14 at 9.24.46 AM.png, Screen Shot
> 2018-06-14 at 9.25.42 AM.png
>
>
> Create a [*React*|https://redux.js.org/basics/usage-with-react] /
> [*Redux*|https://redux.js.org/basics/usage-with-react] prototype of the
> workflow list page. Don't have to handle authentication / authorization for
> now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
