[
https://issues.apache.org/jira/browse/FALCON-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669640#comment-15669640
]
Srikanth Sundarrajan commented on FALCON-2182:
----------------------------------------------
Thanks [~pallavi.rao]. Have a few questions on the design proposal.
1. Noted that the User Parameter Template returns a collection of properties.
Is this fixed to be a collection of properties ? If it merely a illustrative
example and is not meant to be a collection of properties then it looks
alright. There may be issues in fixing this to be a collection of properties,
as it may be restrictive.
2. Why is preparation & submission separated out ? This might lead to users
tampering with the output of the prepared entities and may produce undesirable
results. It might be better to keep them locked down IMHO. I can see the need
for some parameterization, which can be supported through config overlays.
3. Can extensions be removed while being referred to ? I am guessing it should
have an option to be disabled without being removed. As documentation will go
missing if removed completely.
4. Are we thinking of extensions as a convenient way for generating entities or
are we thinking of extensions as a atomic unit of reusable functionality? In
other words, Is extensions role is to only generate the entities and from there
on we simply allow the processes & feeds created to be managed individually or
Are we looking at them as a functional capability and the parts that make them
(collection of processes & feeds) are inseparable ?
> Add support for Falcon user extensions
> --------------------------------------
>
> Key: FALCON-2182
> URL: https://issues.apache.org/jira/browse/FALCON-2182
> Project: Falcon
> Issue Type: New Feature
> Components: extensions
> Reporter: Pallavi Rao
> Attachments: FalconUserExtensions.pdf
>
>
> Currently server-side trusted extensions are supported (see FALCON-634 for
> more details).
> Need to extend the Falcon Extensions to support extensions built by users.
> For example, lets say a user wants to add an extension for "data-quality
> check". This shouldn't require it to be compiled and tested with Falcon
> build. User should be able to add it on-the-fly (while the Falcon Server is
> running) and other users should be able to discover it, and "instantiate"
> this new extension.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
