[
https://issues.apache.org/jira/browse/FALCON-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196892#comment-14196892
]
Venkatesh Seetharam commented on FALCON-672:
--------------------------------------------
Few observations
* why not have a configuration object thats shared among various actions and
transforms?
* Configuration, interface Action - various implementations, interface
transform - various implementations
* Each constructor verifies the schema for each type - EmailAction will expect
to, from, etc.
* This object model is simpler to understand and reduces clutter
* There is NO need for a Primitive. Instead make the interfaces or impl extend
Configured. Please look at the Tool interface in hadoop common
* Simple is beautiful
{noformat}
Configuration - can be reused from hadoop common
Configured
Action -> EmailAction, etc.
Transform -> GroupBy, Filter, Project, etc.
Flow -> ???
{noformat}
* Designer can also be simplified - Use Jersey and remove the RESTImpl, call it
FalconDesignerResource and FalconDesignerClient
> 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)
