[
https://issues.apache.org/jira/browse/NIFI-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197015#comment-16197015
]
Pierre Villard commented on NIFI-4469:
--------------------------------------
I believe this is not a generic issue but something really related to the
MergeContent processor (BinFiles class). On one hand, the validator
{{StandardValidators.POSITIVE_INTEGER_VALIDATOR}} does not allow to set a value
of 0 for instance. On the other hand, it should be possible to tick the
checkbox "set empty string" when configuring the property but the validator
will not allow this option. I think another validator should be used or we
should implement the expected check in the {{customValidate}} method.
> PropertyDesciptors with a default value cannot be unspecified
> -------------------------------------------------------------
>
> Key: NIFI-4469
> URL: https://issues.apache.org/jira/browse/NIFI-4469
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.3.0
> Reporter: Martin Sidery
> Priority: Minor
>
> When removing a value from a component property which has a default value,
> the default value is placed back in to the property on save. This may often
> be the desired behaviour but one instance seen where it is not expected is on
> MergeContent (or any processor that extends BinFiles) where "Maximum Number
> of Entries" resets to 1000 even though it's description says "If not
> specified, there is no maximum."
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
