PATH pattern does not combine well with comma delimination

[alcinnz]

I have a logfile whose lines may include snippets along the line of a=/some/path, b=some/other/path. As an ELK user interested in these logs I would like to parse them with LogStash.

The logstash configuration:

filter {
  grok {
    match => { "message" => "((a=(?<a>%{PATH})?|b=(?<b>%{PATH})?)(,\s)?)+" }
  }
}

when given a=/some/path, b=/some/other/path LogStash gives the output:

{
         "message" => "a=/some/path, b=/some/other/path",
        "@version" => "1",
      "@timestamp" => "2015-02-23T01:57:56.933Z",
            "type" => "stdin",
            "host" => "gallifry",
               "a" => "/some/path,"
}

I expect b to bind to some/other/path:

{
         "message" => "a=/some/path, b=/some/other/path",
        "@version" => "1",
      "@timestamp" => "2015-02-23T01:57:56.933Z",
            "type" => "stdin",
            "host" => "gallifry",
               "a" => "/some/path"
               "b" => "/some/other/path"
}

[alcinnz]

I find that remove all the ?> from the UNIX_PATH pattern fixes this issue.

[purbon]

Fixed in 06de0c1