On initial investigation, it doesn’t seem trivial to enable support for this in
yaml-cpp. It might be feasible to walk the entire parsed yaml tree and map keys
to a to_lower or to_upper key. It would come with some computational and
possibly memory cost, but only at config load time, which shouldn’t be in the
hot path. IMO, the usability improvement would be worth the cost.
On 7/13/17, 11:16 AM, "Marc" <phroc...@apache.org> wrote:
Hi Andy,
I believe this makes sense if Yaml-CPP supports the option, but I would
be cautious if we have to change dependencies. If Yaml-CPP does not support
this are you proposing to make the change to our third party directory?
On Thu, Jul 13, 2017 at 11:09 AM, Andy Christianson <
achristian...@hortonworks.com> wrote:
> All,
>
> It appears that the properties in the config.yml are case-sensitive, and
> to add to it, they’re inconsistent. E.g. in the example from the README.md
> file, we have:
>
> …
> Processors:
> - name: GetFile
> id: 471deef6-2a6e-4a7d-912a-81cc17e3a206
> class: org.apache.nifi.processors.standard.GetFile
> max concurrent tasks: 1
> scheduling strategy: TIMER_DRIVEN
> scheduling period: 1 sec
> penalization period: 30 sec
> yield period: 1 sec
> run duration nanos: 0
> auto-terminated relationships list:
> Properties:
> Input Directory: /tmp/getfile
> Keep Source File: true
> …
>
> The pragmatic course of action would seem to be making the config parser
> case-insensitive, so that users have one less thing to worry about.
>
> If there is no opposition to this, I will enter a Jira ticket to make the
> config parser case-insensitive.
>
> -Andy
>
>
