[
https://issues.apache.org/jira/browse/MINIFI-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351439#comment-15351439
]
ASF GitHub Bot commented on MINIFI-43:
--------------------------------------
GitHub user JPercivall opened a pull request:
https://github.com/apache/nifi-minifi/pull/20
MINIFI-43 Fixing provenance instantiation and making some default con…
…structors private to prevent same problem in other classes
I made the no parameter constructor private when there are required
properties with no default value.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JPercivall/nifi-minifi MINIFI-43
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-minifi/pull/20.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #20
----
commit 1c5c2d49e5e0477a0b6dbb58cbd2c3ecf73b4a52
Author: Joseph Percivall <joeperciv...@yahoo.com>
Date: 2016-06-27T16:52:58Z
MINIFI-43 Fixing provenance instantiation and making some default
constructors private to prevent same problem in other classes
----
> ConfigSchema always instantiates ProvenanceReporter
> ---------------------------------------------------
>
> Key: MINIFI-43
> URL: https://issues.apache.org/jira/browse/MINIFI-43
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
>
> Currently when a flow does set not the Provenance Reporting Task the
> ConfigTransformer will instantiate a ProvenanceReportingSchema the default
> constructor. The problem being there are required properties that don't get
> created and when NiFi attempts to start the reporting task it fails.
> ConfigSchema needs a way to get an optional property that doesn't get
> instantiated when null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
