metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otto Fowler <ottobackwa...@gmail.com>
Subject Re: [GitHub] metron issue #530: METRON-777 Metron Extension System and Parser Extensions
Date Tue, 06 Jun 2017 21:37:54 GMT

Btw. I expounded on this reply in the issue, but no mail is sent out for edits, so please
refer to the pr.

On June 6, 2017 at 17:05:57, ottobackwards (git@git.apache.org) wrote:

Github user ottobackwards commented on the issue: 

https://github.com/apache/metron/pull/530 

@nickwallen I mis-understood your question about what you should be able to do, yes you should
be able to build the nick parser, and put it in parser extensions and add in all the things
nec. to get it installed with the rpms. 

That would be an internal developing metron parser extensions guide ( I don't know what else
to call it, but it is different than creating an extension outside the tree ). 

No. I did not write that all out. Do you feel that is required for this? There is no such
guide presently. Can that be a follow on? 

In the above PR description, I outline the steps required to do what you are asking under
'workflow this enables'. 



--- 
If your project is set up for it, you can reply to this email and have your 
reply appear on GitHub as well. If your project does not have this feature 
enabled and wishes so, or if the feature is enabled but not working, please 
contact infrastructure at infrastructure@apache.org or file a JIRA ticket 
with INFRA. 
--- 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message