falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-672) Design/Implement the client /server api
Date Wed, 05 Nov 2014 03:56:34 GMT

    [ https://issues.apache.org/jira/browse/FALCON-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197451#comment-14197451
] 

Venkatesh Seetharam commented on FALCON-672:
--------------------------------------------

bq. Are you sure you want hadoop-common::Configuration
Well, its out there but depends on what we want to capture here

bq. Generally property bag with String values serialized as xml is too open ended with poor
readability at one end and too restrictive in terms of data types and values that they can
hold in the other end
Again, depends - instead of creating something new, lets iterate with existing infra and then
extend if it does not fit. I'd definitely not have a properties based conf either like in
Falcon

> 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)

Mime
View raw message