Thank you Matt, That is great reply and exactly what I am looking for until 777 PR is in progress.
- Dima On 04/27/2017 01:46 AM, Matt Foley wrote: > Hi Dima, > Regardless of the github release area, etc., the official release repository > for Apache Metron are via the Apache mirrors at > http://www.apache.org/dyn/closer.cgi/incubator/metron/ > soon to be moved to > http://www.apache.org/dyn/closer.cgi/metron/ > > Please go there, pick a mirror, and browse that repository, eg at > http://mirrors.gigenet.com/apache/incubator/metron/ > The numbered top-level subdirectories under these URIs represent released > versions of Metron. By looking at those you can determine the currently > available releases. For a given mirror, you can script the determination. > > The corresponding location for Release Candidates is > https://dist.apache.org/repos/dist/dev/incubator/metron/ > soon to be moved to > https://dist.apache.org/repos/dist/dev/metron/ > > DO NOT DOWNLOAD LARGE OR FREQUENT AMOUNTS OF CONTENT FROM > dist.apache.org/repos/dist/dev/ . It is not mirrored, and is only intended > for developer use. > > Again, the numbering system is obvious. The 0.4.0-RC1 is here, and RC2 will > be going up shortly. > > Once you’ve determined the version you want, you can deduce the github tag > and clone from it, if that is more convenient than using the tarball from the > Apache release repo. > > Hope this helps, > --Matt > > > On 4/26/17, 11:09 AM, "Dima Kovalyov" <dima.koval...@sstech.us> wrote: > > Otto, had a look at 777 PR. Yes, it looks like something we would use. > When do you think it will be released? > > And in meantime the question still stands, is there a way to get current > release id/branch for the script? > Thank you. > > - Dima > > On 04/26/2017 10:56 PM, Otto Fowler wrote: > No, Take a look at METRON-777 PR. > What I want is an extension mechanism, where you can: > > 1. create a project from a metron maven archetype > 2. produce an extension ( parser, enrichment, stellar lib, ?? ) > 3. install that extension through the management UI and configure > > All without touching the metron code. > > > > > On April 26, 2017 at 12:38:28, Dima Kovalyov > (dima.koval...@sstech.us<mailto:dima.koval...@sstech.us>) wrote: > > Regarding parsers and enrichment, new java based topologies for bluecoat, > msexchange, msserver, asa, etc. > > Batching, we use NiFi + Kylo for both stream and batch, but batch data > send to java based tool that passes data through parsers/enrichments classes > and stores in Hive. > > So what you suggesting is to have internal repo with all our changes > alone and to merge it with Apache Metron whenever we need to get full build? > > - Dima > > On 04/26/2017 09:09 PM, Otto Fowler wrote: > Thanks! > > Parsers, and Enrichments, we have a plan or idea about. When you say > extends batch processing… can you say what tech/component/part of stack you > extended? > > New topologies? New WriterBolts? etc? > > I would like as complete a picture as possible of the things for which > anyone would say: > “If I could write this outside the metron tree, i could not have to > maintain a private company fork” > > > > > > On April 26, 2017 at 11:22:21, Dima Kovalyov > (dima.koval...@sstech.us<mailto:dima.koval...@sstech.us>) wrote: > > 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 > > > > > > > >
