[
https://issues.apache.org/jira/browse/METRON-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155520#comment-16155520
]
ASF GitHub Bot commented on METRON-1150:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/729
I'm guessing it probably doesn't replace the changes in the feature branch,
especially if it remove the need for temp path. I'm looking at this as the fix
until that branch comes in, honestly.
I'm +1 by inspection, assuming @ottobackwards is good with it also since
there's impact it sounds like he's a bit worried about.
> REST parseMessage endpoint fails with Unable to load <grok file> from either
> classpath or HDFS
> ----------------------------------------------------------------------------------------------
>
> Key: METRON-1150
> URL: https://issues.apache.org/jira/browse/METRON-1150
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> There was a regression introduced with
> https://github.com/apache/metron/pull/672. Previously the REST application
> would store grok patterns locally when parsing a sample message with the
> GrokParser. Now that REST gets it's HDFS configuration from core-site.xml,
> the GrokParser will always look in HDFS. As a result, the REST app should
> store temporary grok files in HDFS instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
