Is there an equivalent disclaimer for full products?
On June 26, 2017 at 21:53:34, Nick Allen (n...@nickallen.org) wrote:
> +1 Yes, definitely cruft. Good find.
>
> On Mon, Jun 26, 2017 at 9:50 PM, Matt Foley wrote:
>
> The Release Process document at https://cwiki.apache.org/
> confluence/displ
+1 Yes, definitely cruft. Good find.
On Mon, Jun 26, 2017 at 9:50 PM, Matt Foley wrote:
> The Release Process document at https://cwiki.apache.org/
> confluence/display/METRON/Release+Process
> currently states that a file named DISCLAIMER is a required artifact in
> the release package. The
The Release Process document at
https://cwiki.apache.org/confluence/display/METRON/Release+Process
currently states that a file named DISCLAIMER is a required artifact in the
release package. The contents of this file are:
===
Apache Metron is an effort undergoing incubation at The Apache Softwa
There are 135 jiras with patches committed to 0.4.0 in github. They may be
queried via the somewhat large JQL search below.
Most of them are marked “DONE”, but have no “Fix Version”. I will mark them as
fixed in “0.4.0” per our SOP. If you know that some Jira is marked DONE but
isn’t really
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/530
@ottobackwards , in general (a) make it work in github, and (b) make sure
the human-readable link reference text is the same as the human-readable anchor
text. That way the site-book generator
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
I have started building out the readme's. but I'm having trouble getting
linking to work from the a README.md -> ./another-file.md and from README.md
| another-file.md to third-file#ANCHOR.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@mmiklavc regarding "I'm not sure I fully understand the difference between
the concepts of bundle, assembly, extension, and component yet. It would be
really helpful if you could add an archit
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r124111822
--- Diff: metron-analytics/metron-maas-service/README.md ---
@@ -138,7 +138,7 @@ Now that we have a deployed model, let's adjust the
configurations for the
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r124111690
--- Diff:
metron-platform/metron-extensions/metron-parser-extensions/metron-parser-bro-extension/metron-parser-bro-assembly/src/main/assembly/assembly.xml
---
Matt, I think we have been waiting for a reply from Christian for a while. I
would like to proceed with the build and if he chimes in we can include his PR
in the next release.
26.06.2017, 10:17, "Matt Foley" :
> Hi all,
> I am proceeding with building the 0.4.0 release candidate, from current
Hi all,
I am proceeding with building the 0.4.0 release candidate, from current HEAD of
master.
Christian, still looking forward to getting the improvements for the PaloAlto
parser in, in testable form. If you’re not going to be able to fix the unit
tests presently, please tell the community s
GitHub user justinleet reopened a pull request:
https://github.com/apache/metron/pull/624
[DO NOT MERGE] METRON-1004: Travis CI - Job Exceeded Maximum Time Limit
## Contributor Comments
Given that Apache travis fails more often, I'm using this PR to hopefully
hit the skidoo clau
Github user justinleet closed the pull request at:
https://github.com/apache/metron/pull/624
---
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
This problem is not uncommon, I would think. This should be implemented as
‘clean’ as possible such that it can be spun out.
It would also be a candidate for a feature/collaboration/long branch
On June 26, 2017 at 12:44:44, Casey Stella (ceste...@gmail.com) wrote:
When we're talking about a "tr
When we're talking about a "transaction log", an edit could involve
multiple delete/additions, so are we proposing storing a diff to the JSON
map as the representation of a particular transaction? I proposed
pre-caching the current value to lessen the burden on the reader (i.e. not
having to merge
It is clear to me that we need an independently-stored transaction log that is
de-coupled from any of our existing systems. So Simon’s idea of storing the
transaction logs in Hbase and being able to reference them via a global ID
resonates with me. I like it for the following reasons:
- It ma
Github user cestella closed the pull request at:
https://github.com/apache/metron/pull/621
---
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 en
GitHub user cestella reopened a pull request:
https://github.com/apache/metron/pull/621
METRON-1001: Allow metron to ingest parser metadata along with data
## Contributor Comments
Currently, we only ingest data in Metron. Often, there is valuable metadata
constructed up-stream o
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/624
This looks really good. After trying to find a better 'use' or
'sequencing' to resolve some problems - and failing - I am really glad to see
this.
I do have a couple of things I have
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
I moved work from a mostly unrelated branch over here. Specifically, it
attempts to get the InMemoryComponents to be reused across a given test class.
This is particularly helpful for ProfilerIn
GitHub user cestella reopened a pull request:
https://github.com/apache/metron/pull/621
METRON-1001: Allow metron to ingest parser metadata along with data
## Contributor Comments
Currently, we only ingest data in Metron. Often, there is valuable metadata
constructed up-stream o
Github user cestella closed the pull request at:
https://github.com/apache/metron/pull/621
---
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 en
Github user cestella closed the pull request at:
https://github.com/apache/metron/pull/621
---
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 en
GitHub user cestella reopened a pull request:
https://github.com/apache/metron/pull/621
METRON-1001: Allow metron to ingest parser metadata along with data
## Contributor Comments
Currently, we only ingest data in Metron. Often, there is valuable metadata
constructed up-stream o
Github user iraghumitra commented on the issue:
https://github.com/apache/metron/pull/526
@merrimanr Here is the list of consolidated suggestion on this PR. I worked
on the comments that are related to code guidelines and readability of the
code. As for improving coverage, i can submi
25 matches
Mail list logo
