[
https://issues.apache.org/jira/browse/MINIFI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Percivall updated MINIFI-1:
----------------------------------
Comment: was deleted
(was: For the initial proof of concept (MINIFI-5), the underlying framework
should re-use the nifi.properties and flow.xml* for configuration but we
should offer a more use friendly config file to be able to set all the
pertinent properties. My idea is to have "config.yml" that outlines all the
properties for configuring and starting up NiFi with a ConfigTransformer that
is called by bootstrap.java (or other startup class), takes in the config.yml
and writes out the flow.xml and nifi.properties.
I suggested a Yaml file because it is very user friendly and has very good
libraries to use.
* I did not include bootstrap.conf because all the configuration in there is
necessary to start the JVM which, in my view, is outside the scope something a
user would regularly set.)
> Establish a processing flow configuration interface for supporting design and
> deploy
> -------------------------------------------------------------------------------------
>
> Key: MINIFI-1
> URL: https://issues.apache.org/jira/browse/MINIFI-1
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Components: Processing Configuration
> Reporter: Aldrin Piri
> Fix For: 0.0.1
>
> Attachments: ConfigFileExplanation.xml, config.yml
>
>
> An interface is needed for establishing configuration items and changes from
> multiple sources whether they be file, based on a given protocol, or similar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
