Hi Navina,
Yes, I'm seeing the issue on 0.8.0. As I mentioned in the bug, I know the
method of passing the config is changing, but I still wanted to get the issue
on record. With regard to Util.envVarEscape(), the assumption seems to be that
the value is going through the shell at some point,
Hi Tommy,
I wouldn't think Util.envVarEscape() is totally unnecessary. Are you
running into this issue with a version <= 0.9 ?
With 0.10, I think we no longer pass all the environment variables through
command line. We only pass the Coordinator system information via command
line.
While Util.env
Ok, the issue with spaces appears to have been addressed by
https://issues.apache.org/jira/browse/SAMZA-530. But quotes are still a
problem, and I'm becoming increasingly convinced that Util.envVarEscape()
method is unnecessary.
On 06/08/2015 03:02 PM, Tommy Becker wrote:
We have a stream job
We have a stream job that uses an MVEL expression to filter messages to
process. The expression is passed through the Config, and I noticed that the
expressions were often getting mangled and/or blowing up the job. I've seen
issues with at least 2 characters, quotes and spaces. In version 0.
