[
https://issues.apache.org/jira/browse/MINIFI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218265#comment-15218265
]
Joseph Percivall commented on MINIFI-2:
---------------------------------------
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.
> File based implementation
> -------------------------
>
> Key: MINIFI-2
> URL: https://issues.apache.org/jira/browse/MINIFI-2
> Project: Apache NiFi MiNiFi
> Issue Type: Sub-task
> Components: Processing Configuration
> Reporter: Aldrin Piri
> Fix For: 0.0.1
>
>
> A defined schema for processing configuration will need to be defined. XML
> or YAML seem like possible options for achieving this.
> Agent configuration will come from two places, a bootstrap properties file
> and a flow configuration file. The bootstrap will make use of some of the
> original nifi.properties in order to start up the agent. The flow
> configuration file will essentially be a stripped down version of a flow.xml
> (with potentially S2S properties from nifi.properties).
> The format for the bootstrap.properties should likely be similar to
> nifi.properties.
> Further, a way to incorporate this to leverage the libraries from core NiFi
> will aid in achieving a proof of concept implementation more expediently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
