falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "samar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-387) Rest APIs to render the Designer UI
Date Mon, 28 Apr 2014 09:28:14 GMT

     [ https://issues.apache.org/jira/browse/FALCON-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

samar updated FALCON-387:
-------------------------

    Attachment: FALCON-322_1.patch

Initial code containing the basic layour

> Rest APIs to render the Designer UI
> -----------------------------------
>
>                 Key: FALCON-387
>                 URL: https://issues.apache.org/jira/browse/FALCON-387
>             Project: Falcon
>          Issue Type: Sub-task
>            Reporter: samar
>         Attachments: FALCON-322_1.patch
>
>
> We need CRUD apis for FLOWS
> Each flow would contain a list of transformations
> We need a rest api to get the list of transformation (to start with it would return a
static list of transformation)
> Each transformation need to be mapped to a UI element for a custom view
> We need a rest api to get the list of actions
> After the creation of flow(sequence of transformation applied to a feed) , flow object
should be serialised on the GWT end and send to FalconDesignerRestServer to compile
> A concrete implementation of a configuration object would exist per transformation. The
configuration object will help us populate the UI elements
> FalconDesignerRestServer will expose a rest api to compile which will return success
or errors
> FalconDesignerRestServer also need to expose a rest api to deploy the flow
> Flows will be saved as different version. 
> Flows are organised under folders(UI representation). It can be passed as another property
e.g. group=analytics. 
> Action items
> Create a rest App(FalconDesignerRestServer)
> Expose following APIs
> expose CRUD apis for FLOWS
> getFlow() api should pass a version . if no versions is passed then the default(latest
version) should be returned.
> list all transformations
> Creating UI elements per transformation/action and store the mapping  of transformation
to the related UI element.
> list all Actions
> compile a flow
> provision a flow
> Methods to 
> Serialise a flow. Which would internally serialze the list of transformations
> To start with we will create dummy rest apis to unblock UI development



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message