[
https://issues.apache.org/jira/browse/METRON-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155846#comment-16155846
]
ASF GitHub Bot commented on METRON-1150:
----------------------------------------
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/729#discussion_r137353301
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/configuration/metron-rest-env.xml
---
@@ -90,17 +90,11 @@
</property>
<property>
<name>metron_temp_grok_path</name>
- <description>Temporary local file path where grok patterns are
written during testing</description>
- <value>./patterns/temp</value>
+ <description>Temporary HDFS file path where grok patterns are
written during testing</description>
--- End diff --
No. The parse and init methods are called directly on the configured
MessageParser class so there is no need to persist a tmp parser config or
anything like that.
> 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)
