[
https://issues.apache.org/jira/browse/NIFI-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Rosander updated NIFI-3092:
---------------------------------
Description:
The toolkit bat files currently don't quote the command line arguments passed
to them. This results in problems with spaces or special characters as
arguments.
We should be able to address this by double-quoting the cmd arguments. If we
add a space before the closing "", we should be able to handle whether or not
the last argument is quoted.
E.g. without spaces -n "localhost(2)" would be rendered as -n "localhost(2)"""
which breaks but with space it will be -n "localhost(2)" "" which is
interpreted correctly.
See
http://stackoverflow.com/questions/12891383/correct-quoting-for-cmd-exe-for-multiple-arguments#answer-12892791
was:
The toolkit bat files currently don't quote the command line arguments passed
to them. This results in problems with spaces or special characters as
arguments.
We should be able to address this by double-quoting the cmd arguments. If we
add a space before the closing "", we should be able to handle whether or not
the last argument is quoted.
E.g. without spaces -n "localhost(2)" would be rendered as -n "localhost(2)"""
which breaks but with space it will be -n "localhost(2)" "" which is
interpreted correctly.
> NiFi Toolkit bat files should quote command line args properly
> --------------------------------------------------------------
>
> Key: NIFI-3092
> URL: https://issues.apache.org/jira/browse/NIFI-3092
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Bryan Rosander
> Assignee: Bryan Rosander
>
> The toolkit bat files currently don't quote the command line arguments passed
> to them. This results in problems with spaces or special characters as
> arguments.
> We should be able to address this by double-quoting the cmd arguments. If we
> add a space before the closing "", we should be able to handle whether or not
> the last argument is quoted.
> E.g. without spaces -n "localhost(2)" would be rendered as -n
> "localhost(2)""" which breaks but with space it will be -n "localhost(2)" ""
> which is interpreted correctly.
> See
> http://stackoverflow.com/questions/12891383/correct-quoting-for-cmd-exe-for-multiple-arguments#answer-12892791
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
