[
https://issues.apache.org/jira/browse/FALCON-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880054#comment-13880054
]
Srikanth Sundarrajan commented on FALCON-259:
---------------------------------------------
1. compile & validate does apply to all primitives (which includes flows,
transforms & actions)
2. If the object used, implements toString(), it would show up with appropriate
value (else will show up default object::toString(), which isn't very helpful)
3. Yes, the idea is to provide all the errorMessages in one go. Validate
collects all the errors and compile throws an exception with that collection on
first error.
4. doCompile is internal, and it is expected for each primitive to implement
this (hence abstract).
5. Transform should have the ability to produce multiple outputs. Agreed. Will
rework this
6. Since version is an int, hashcode can be the same value.
7. Good question. In practice, it might be hard to construct the version object
as the version also includes timestamp. I can fix it to include Version, and
see if it gets difficult to work with this contract and react.
> Design Transformation Interface
> -------------------------------
>
> Key: FALCON-259
> URL: https://issues.apache.org/jira/browse/FALCON-259
> Project: Falcon
> Issue Type: Sub-task
> Components: designer
> Affects Versions: 0.5
> Reporter: Srikanth Sundarrajan
> Assignee: Srikanth Sundarrajan
> Attachments: FALCON-259.patch
>
>
> The foundation block in the pipeline designer is the transformation. All
> primitives of the process are either defined as a transformation or an
> action. Transformation is a data flow primitive while action could either be
> a general purpose processing primitive or a control flow.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
