[
https://issues.apache.org/jira/browse/MINIFICPP-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893799#comment-16893799
]
Mr TheSegfault edited comment on MINIFICPP-985 at 7/26/19 12:52 PM:
--------------------------------------------------------------------
Maybe this will help me resolve my confusion. It sounds like allowable values
cannot be used in cases where we have a defined set of choices? Why is that?
Also this seems like a good thing to discuss for 0.8.0 or 0.9.0 as we seem to
have a small disagreement about risk ( mine is semantic risk ) – so I removed
the version modifier. I saw the POC pr, appreciate the work
was (Author: phrocker):
Maybe this will help me resolve my confusion. It sounds like allowable values
cannot be used in cases where we have a defined set of choices? Why is that?
> Implement listvalidators
> ------------------------
>
> Key: MINIFICPP-985
> URL: https://issues.apache.org/jira/browse/MINIFICPP-985
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Affects Versions: 0.6.0
> Reporter: Arpad Boda
> Assignee: Arpad Boda
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As [~nghiaxlee] pointed out in a change we don't have the functionality to
> create list validators (in which case all elements of the input lists should
> be validated using an encapsulated validator), so we can't validate multiple
> choice properties for eg.
> The change itself is quite easy, although we should keep in mind C2
> integration. Because of this [~phrocker] and [~kdoran] I would like to ask
> for your feedback on adding this into agent manifest. Thanks in advance!
> I scoped this for 0.7.0 as the MiNiFi impact would be small, however I can
> accept rescheduling it to 0.8.0 in case C2 integration requires more effort
> and testing.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
