[
https://issues.apache.org/jira/browse/FALCON-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197763#comment-14197763
]
samar commented on FALCON-672:
------------------------------
[~svenkat] We current have a Configuration(not Hadoop Config) object which
everyone else is extending.
https://issues.apache.org/jira/secure/attachment/12667164/flow_object_model.jpg
. There ActionConfig , TransformConfig , EmailActionConfig and so on. This only
contains the configuration and not functionality. The functionality will be
held by respective Primitives -> Email , JSM , JOIN and so . Primitives will
only exist on the server side which the config can be exchanged (JSON
representation or object) .
Use Jersey and remove the RESTImpl, call it FalconDesignerResource and
FalconDesignerClient
>>>> Already using Jersey . Will refactor it to FalconDesignerResource
> Design/Implement the client /server api
> ---------------------------------------
>
> Key: FALCON-672
> URL: https://issues.apache.org/jira/browse/FALCON-672
> Project: Falcon
> Issue Type: Sub-task
> Components: designer
> Reporter: samar
> Attachments: falcon_desinger_api_design.jpg, flow_object_model.jpg,
> primitive_class_diagram.gif
>
>
> Design/Implement the client /server api which will be exposed by the server
> and will be used by any client to interact with designer. This would include
> the final data model and the service contract
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
