Otto, Yes, we developed custom parsers and enrichments (in future we seek to open source them, but have no time to up them to the decent level currently). We also merged our custom tools that extends Metron batching processing and store data in HDFS and Hive to be used by tableau, zeppelin, etc.
Is that answers your question? Let me know if you want to know more. - Dima On 04/26/2017 08:29 PM, Otto Fowler wrote: Can I ask Dima, as comfortable you are in describing, what areas do you make changes or additions to that require you to maintain a fork? Custom parsers? Enrichments? Other? I have done some work, and have more planned and lined up to try to eliminate the requirement to develop in the metron tree to extend the product, and would be interested in your cases. On April 26, 2017 at 10:46:03, Dima Kovalyov (dima.koval...@sstech.us<mailto:dima.koval...@sstech.us>) wrote: Hello, We want to merge latest metron release branch with out develpoment every time it is get released. What is the path we should take here in order to identify what release happened successfully? Latest release is 0.3.1 currently, but since you're preparing for 0.4.0 (which will take a while) following links already have 0.4.0: https://github.com/apache/incubator-metron/blob/master/pom.xml https://github.com/apache/incubator-metron/releases The only place I have found with 0.3.1 (current latest release) is: https://metron.apache.org/documentation/#releases But there is no way for a script to figure what commit or branch to pick up from github for merging. Can you please suggest? Thank you. - Dima
