[
https://issues.apache.org/jira/browse/UIMA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406564#comment-15406564
]
Eddie Epstein commented on UIMA-5032:
-------------------------------------
A feature toggle would often be at an aggregate level, that is, a delegate AAE
would be disabled. This would not be convenient to do if implemented at the
level of a primitive AE as all AAE primitives would have to be independently
disabled; much easier to control at flow controller perspective.
Then there is the issue of modifying flow controllers. An aggregate with
CasMultipliers has multiple flow paths, one for the parent and one for each
type of child CAS. It might be easiest to have a reserved name flow controller
configuration parameter used to list the disabled delegates, and support wild
cards that would allow disabling everything. There are then two ways to use
this configuration value: 1- the flow controller ignores those delegates and
lazy initialization skips the init overhead, or 2- the aggregate controller
(ASB) could use this parameter value to bypass initialization, destroy and CPC
calls, and drop delegates from the aggregate context; disabled delegates would
be invisible to the flow controller, and this approach would work without lazy
initialization.
> Support feature toggle using lazy annotator initialization
> -----------------------------------------------------------
>
> Key: UIMA-5032
> URL: https://issues.apache.org/jira/browse/UIMA-5032
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Eddie Epstein
>
> Feature toggle is a useful technique to have a single source stream for both
> production and development activities. One approach for UIMA to help support
> feature toggle would be to do component initialization only on the first
> process call. Lazy initialization would allow flow controller configuration
> to easily turn components on and off.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
