date:20170411

GitHub user mattf-horton opened a pull request:

https://github.com/apache/incubator-metron/pull/525

METRON-845 Increment build number to 0.4.0

Simply replaced all effective Metron version strings, from "0.3.2" to 
"0.4.0".
Used `mvn versions:set -DnewVersion=0.4.0` first, then did
```
for f in `grep -r -l "0\.3\.1" * | egrep -v '^site/'` ; do  echo " "; echo 
$f; grep "0\.3\.1" $f; done
```
to catch the non-maven files, and hand-edited them.
The remaining handful of .md and log files containing "0.3.2" are not 
effective Metron versions, but recordings of previous uses, so they are not 
changed.

NOTE: The new branch has not propagated to github, presumably because only 
commits stimulate the propagation, and a new branch copied from existing master 
is not technically a commit.  So we are using this low-risk commit to cause 
that propagation, even though it needs a few more hours to run full tests.


## Pull Request Checklist
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [x] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?


### For code changes:
- [NA] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [NA] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [x] (IN PROCESS) Have you ensured that the full suite of tests and checks 
have been executed in the root incubating-metron folder via:
  ```
  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  ```

- [NA] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [NA] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] (IN PROCESS) Have you verified the basic functionality of the build 
by building and running locally with Vagrant full-dev environment or the 
equivalent?

### For documentation related changes:
- [NA] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mattf-horton/incubator-metron METRON-845

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-metron/pull/525.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #525


commit ad16caf4bca1cdc2a9e573378981c37b29dcce20
Author: mattf-horton 
Date:   2017-04-12T05:02:59Z

METRON-845 Increment build number to 0.4.0




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [MENTORS] Licensing

2017-04-11 Thread zeo...@gmail.com

Oh awesome, thanks Nick.  I guess it just took another day (or at least
several additional hours) for it to be created.

Jon

On Tue, Apr 11, 2017, 3:51 PM Nick Allen  wrote:

> I think that was done with the original request.
>
> https://github.com/apache/incubator-metron-bro-plugin-kafka
>
>
>
>
> On Mon, Apr 10, 2017 at 8:59 PM, zeo...@gmail.com 
> wrote:
>
> > Okay great, thanks you.  I've sent an email out to general@ to discuss.
> >
> > It looks like things are all set up on asf
> >  > metron-bro-plugin-kafka.git>
> > for
> > that new repo - would somebody be willing to setup a read-only git mirror
> > to github ?  My
> > understanding is that I'm unable to make this request myself, as I am
> not a
> > PMC member.  The documentation that I've been able to find says:
> >
> > Please file an INFRA  issue
> > (component: Git) to request a new codebase to be mirrored or to change
> the
> > settings of an existing mirror. When requesting a new mirror, please
> > include the following information:
> >
> >-
> >
> >Name of the codebase, for example "Apache Tika"
> >-
> >
> >Name of the requested Git mirror, for example "tika.git"
> >-
> >
> >Subversion path of the codebase, for example "/lucene/tika"
> >-
> >
> >Subversion layout, in case it is different from the standard "trunk,
> >branches, tags" structure.
> >
> >
> > If this is something that I should be able to do I would be more than
> happy
> > to, just let me know.  Thanks!
> >
> > Jon
> >
> > On Mon, Apr 10, 2017 at 4:19 PM P. Taylor Goetz 
> wrote:
> >
> > > In my opinion, I think you are probably okay including it. You would
> want
> > > to retain any license headers, and also make sure your NOTICE file is
> > > updated to include the copyright information.
> > >
> > > I’m not by any means an expert in these matters, so I would recommend
> > > getting a second opinion by leveraging the collective intelligence of
> the
> > > general@incubator (while you are a podling or even afterward) or
> > > legal-discuss@. The latter list is often home to some important legal
> > > discussions, and I would recommend PMC members read and/or subscribe to
> > > that list.
> > >
> > > -Taylor
> > >
> > > > On Apr 5, 2017, at 4:50 PM, zeo...@gmail.com 
> wrote:
> > > >
> > > > *Background*
> > > > We have a situation where a portion of code
> > > > <
> > > https://github.com/apache/incubator-metron/tree/master/
> > metron-sensors/bro-plugin-kafka
> > > >
> > > > was created for Metron, which is a plugin for a separate open source
> > > > project, bro.  The code was separately pushed out by the initial
> author
> > > to
> > > > the bro community under the 3-Clause BSD license
> > > > , and
> > > > some important
> > > > enhancements
> > > > <
> > >
> https://github.com/bro/bro-plugins/commit/b9f1f35415cb0db065348da0a5043a
> > 8353b4a0a8
> > > >
> > > > have been made to it in that separate community, which we would like
> to
> > > > include, in addition to some recent changes
> > > > <
> > > https://github.com/apache/incubator-metron/commit/
> > a2452a25caffdd8c35fd9efe0ed49ce0dd2e3781
> > > >
> > > > that have been made in the Metron code base as well (i.e. we are not
> > > simply
> > > > pulling the code down from the external project).  This was discussed
> > > > recently
> > > > <
> > > https://lists.apache.org/thread.html/c92acd125dae05f0537d4505e0254d
> > fa6382ca9f40edba7d2f4c6224@%3Cdev.metron.apache.org%3E
> > > >
> > > > on the dev mailing list, and we wanted to get some clarification
> before
> > > > moving forward.
> > > >
> > > > *Questions*
> > > > 1. Is it valid to assume that, as Casey mentioned
> > > > <
> > > https://lists.apache.org/thread.html/7468692c96ed0cb012ac9014229694
> > ba8edf3a3b3b55d346eec57019@%3Cdev.metron.apache.org%3E
> > > >,
> > > > these are two separate plugins and we can simply make modifications
> to
> > > our
> > > > code base to resolve the current multithreading issue?
> > > >
> > > > 2. If we do 1, will this require a line in our LICENSE file as a
> > > derivative
> > > > work?
> > > >
> > > > Anyone, feel free to correct my historical understanding here - I
> > wasn't
> > > > closely involved with the project at the time this all occurred.
> > Thanks,
> > > >
> > > > Jon
> > > > --
> > > >
> > > > Jon
> > >
> > > --
> >
> > Jon
> >
>
-- 

Jon

Re: [DISCUSS] Extracting Stellar as a component/module

2017-04-11 Thread Matt Foley

I’ve copied it to the cwiki, but the thing is that cwiki only allows comments
at the bottom. With a long doc like this, that’s not very good. I’d much
rather keep everyone’s comments in the same system, and local to the text
they’re commenting on.

Is it okay to leave this in google doc?

If anyone can’t abide logging in to google, the cwiki version is here:

https://cwiki.apache.org/confluence/display/METRON/Extracting+Stellar+into+an+Independent+Module

Thanks,

--Matt

On 4/11/17, 3:15 PM, "Matt Foley" wrote:

No, actually you’re right. Will have it moved over shortly.

On 4/11/17, 2:56 PM, "Otto Fowler" wrote:

Nevermind

On April 11, 2017 at 17:47:57, Otto Fowler (ottobackwa...@gmail.com)
wrote:

Can’t we do this in confluence?

On April 11, 2017 at 17:38:40, Matt Foley (ma...@apache.org) wrote:

Hi all,

This is a new discussion thread, and if the proposed change is accepted
by

the community, it will be submitted to the next release, not the current

0.4.0 branch.

Stellar has 126 verbs today, and seems only likely to continue growing.

Furthermore, we expect Stellar to be extended by users, and probably
grow

into having one or more Registry/ Repositories, etc. All this suggests
that

we should start viewing Stellar itself as a component, and make sure it
is

maintainable and has clean interfaces to the rest of the system. And
that

will be easier if we extract it into its own module, both in the code
tree

and in maven.

I’ve written a combination proposal / discussion about how to extract

Stellar from its current deep embed in Metron. Comments are welcome, and

encouraged. Please read:

https://docs.google.com/document/d/1EP7Jt4ePHe2A-_oboLl2QbN1muh7uKeET_kbpIgjcJM/edit#heading=h.4vsrmths49wk

I believe I’ve set access so anyone can read and comment on it. However,

google docs may still ask you log in with a google-registered email

address. If this is a problem for anyone, let me know and I can send
you a

Word document.

Thanks,

--Matt

Re: [DISCUSS] Extracting Stellar as a component/module

Nevermind


On April 11, 2017 at 17:47:57, Otto Fowler (ottobackwa...@gmail.com) wrote:

Can’t we do this in confluence?



On April 11, 2017 at 17:38:40, Matt Foley (ma...@apache.org) wrote:

Hi all,
This is a new discussion thread, and if the proposed change is accepted by
the community, it will be submitted to the next release, not the current
0.4.0 branch.

Stellar has 126 verbs today, and seems only likely to continue growing.
Furthermore, we expect Stellar to be extended by users, and probably grow
into having one or more Registry/ Repositories, etc. All this suggests that
we should start viewing Stellar itself as a component, and make sure it is
maintainable and has clean interfaces to the rest of the system. And that
will be easier if we extract it into its own module, both in the code tree
and in maven.

I’ve written a combination proposal / discussion about how to extract
Stellar from its current deep embed in Metron. Comments are welcome, and
encouraged. Please read:
https://docs.google.com/document/d/1EP7Jt4ePHe2A-_oboLl2QbN1muh7uKeET_kbpIgjcJM/edit#heading=h.4vsrmths49wk

I believe I’ve set access so anyone can read and comment on it. However,
google docs may still ask you log in with a google-registered email
address. If this is a problem for anyone, let me know and I can send you a
Word document.

Thanks,
--Matt

Re: [DISCUSS] Extracting Stellar as a component/module

Can’t we do this in confluence?



On April 11, 2017 at 17:38:40, Matt Foley (ma...@apache.org) wrote:

Hi all,
This is a new discussion thread, and if the proposed change is accepted by
the community, it will be submitted to the next release, not the current
0.4.0 branch.

Stellar has 126 verbs today, and seems only likely to continue growing.
Furthermore, we expect Stellar to be extended by users, and probably grow
into having one or more Registry/ Repositories, etc. All this suggests that
we should start viewing Stellar itself as a component, and make sure it is
maintainable and has clean interfaces to the rest of the system. And that
will be easier if we extract it into its own module, both in the code tree
and in maven.

I’ve written a combination proposal / discussion about how to extract
Stellar from its current deep embed in Metron. Comments are welcome, and
encouraged. Please read:
https://docs.google.com/document/d/1EP7Jt4ePHe2A-_oboLl2QbN1muh7uKeET_kbpIgjcJM/edit#heading=h.4vsrmths49wk

I believe I’ve set access so anyone can read and comment on it. However,
google docs may still ask you log in with a google-registered email
address. If this is a problem for anyone, let me know and I can send you a
Word document.

Thanks,
--Matt

[DISCUSS] Extracting Stellar as a component/module

2017-04-11 Thread Matt Foley

Hi all,
This is a new discussion thread, and if the proposed change is accepted by the 
community, it will be submitted to the next release, not the current 0.4.0 
branch.

Stellar has 126 verbs today, and seems only likely to continue growing.  
Furthermore, we expect Stellar to be extended by users, and probably grow into 
having one or more Registry/ Repositories, etc.  All this suggests that we 
should start viewing Stellar itself as a component, and make sure it is 
maintainable and has clean interfaces to the rest of the system.  And that will 
be easier if we extract it into its own module, both in the code tree and in 
maven.

I’ve written a combination proposal / discussion about how to extract Stellar 
from its current deep embed in Metron.  Comments are welcome, and encouraged.  
Please read:
https://docs.google.com/document/d/1EP7Jt4ePHe2A-_oboLl2QbN1muh7uKeET_kbpIgjcJM/edit#heading=h.4vsrmths49wk

I believe I’ve set access so anyone can read and comment on it.  However, 
google docs may still ask you log in with a google-registered email address.  
If this is a problem for anyone, let me know and I can send you a Word document.

Thanks,
--Matt

[GitHub] incubator-metron pull request #524: METRON-836 Use Pycapa with Kerberos

2017-04-11 Thread nickwallen

GitHub user nickwallen opened a pull request:

https://github.com/apache/incubator-metron/pull/524

METRON-836 Use Pycapa with Kerberos

This PR makes the necessary changes for Pycapa to work in a Kerberized 
environment.  
* The previous Kafka client library used by Pycapa did not support 
Kerberos.  Switched to another that supports Kerberos and is based on 
librdkafka, which is the same library used by Fastcapa and the Bro Plugin.
* Added docs on how to install and setup Pycapa for Kerberos.
* Added lots of additional docs around usage.

I tested this change on plain-vanilla Quick Dev, a kerberized-Quick Dev and 
also a bare-metal cluster that is using Kerberos.

## Pull Request Checklist

- [x] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [x] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
- [x] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been 
executed in the root incubating-metron folder via:
- [x] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?
- [x] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:




You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nickwallen/incubator-metron METRON-836

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-metron/pull/524.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #524


commit f481ed3787c79a897ae3eca1bbde4451abfceec3
Author: Nick Allen 
Date:   2017-04-10T15:10:02Z

METRON-836 Use Pycapa with Kerberos




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: metron UI

2017-04-11 Thread Laurens Vets


These are the errors I see when don't use the http option:

[HPM] Error occurred while trying to proxy request /api/v1/user from 
node1:4200 to 192.168.66.121:8082 (EINVAL) 
(https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /api/v1/user from 
node1:4200 to 192.168.66.121:8082 (EINVAL) 
(https://nodejs.org/api/errors.html#errors_common_system_errors)


On 2017-04-11 14:08, Ryan Merriman wrote:

The -r option shouldn't be that sensitive. Separate host and port
properties would be better.

On Tue, Apr 11, 2017 at 4:04 PM, Laurens Vets  
wrote:



On 2017-04-11 12:44, zeo...@gmail.com wrote:


   scp

./metron-interface/metron-config/target/metron-config-0.3.1-
archive.tar.gz
root@node1:/usr/metron/0.3.1/
   ssh root@node1
   cd /usr/metron/0.3.1/
   tar -xf metron-config-0.3.1-archive.tar.gz
   yum install -y npm
   npm install npm@3.8.9 -g
   export METRON_REST_URL=http://node1:8082
   ./bin/start_management_ui.sh

   I had to make sure to specify "-p 4200 -r http://node1:8082; to
server.js



FYI, if you use "-r node1:8082" instead of "-r http://node1:8082;, you
can't login. I had to find that out the hard way.

[GitHub] incubator-metron pull request #516: METRON-830 Adding StringFunctions to Ste...

Github user mattf-horton commented on a diff in the pull request:

https://github.com/apache/incubator-metron/pull/516#discussion_r111012694
  
--- Diff: metron-platform/metron-common/README.md ---
@@ -167,6 +172,14 @@ The `!=` operator is the negation of the above.
 | [ `WEEK_OF_YEAR`](#week_of_year) 
  |
 | [ `YEAR`](#year) 
  |
 
+### `APPEND_IF_MISSING`
+  * Description: Appends the suffix to the end of the string if the string 
does not already end with any of the suffixes.
+  * Input:
+* string - The string to be appended.
+* suffix - The string suffix to append to the end of the string.
+* suffixes - Optional - Additional string suffixes that are valid 
terminators.
--- End diff --

Ah, got it.  The documentation you point at for apache commons 
PrependIfMission method actually uses signature:
```
CharSequence... suffixes
```
so it is a varargs usage.  You can do the same with Stellar, or we have 
found it better to allow a list of strings instead (which you would explode 
into the calling varargs in the java code).  Using a list instead of varargs 
makes it much easier to extend the function later if we choose.

It's up to you whether to do this now.  We are trying to close a RC, so 
there is some time pressure.  Maybe you should just open a jira to enhance this 
later with a list arg.  

The current implementation of your call to PrependIfMissing is such that 
the "additionalsuffix" description you suggest would be correct.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request #516: METRON-830 Adding StringFunctions to Ste...

2017-04-11 Thread anandsubbu

Github user anandsubbu commented on a diff in the pull request:

https://github.com/apache/incubator-metron/pull/516#discussion_r110992116
  
--- Diff: metron-platform/metron-common/README.md ---
@@ -167,6 +172,14 @@ The `!=` operator is the negation of the above.
 | [ `WEEK_OF_YEAR`](#week_of_year) 
  |
 | [ `YEAR`](#year) 
  |
 
+### `APPEND_IF_MISSING`
+  * Description: Appends the suffix to the end of the string if the string 
does not already end with any of the suffixes.
+  * Input:
+* string - The string to be appended.
+* suffix - The string suffix to append to the end of the string.
+* suffixes - Optional - Additional string suffixes that are valid 
terminators.
--- End diff --

Hi @mattf-horton , I was trying to following the same wording as the 
[apache commons 
documentation](https://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringUtils.html)
 for PrependIfMissing, which uses the plural form. 

Let me know if it would be better if I changed the text as follows:

`* suffix - The string suffix to append to the end of the string.`
`* additionalsuffix - Optional - An additional string suffix that is a 
valid terminator.`


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] next release proposal

2017-04-11 Thread Casey Stella

+1 to 0.4.0

On Tue, Apr 11, 2017 at 2:03 PM, Otto Fowler 
wrote:

> +1
>
>
> On April 11, 2017 at 13:59:46, Matt Foley (ma...@apache.org) wrote:
>
> Hi all,
> Looks to me like the vast majority of the material mentioned below has been
> committed. There are still 8 recent PRs that need review and, hopefully,
> commit.
>
> I’m going to go ahead and make a release branch, with the understanding
> that any further commits (especially but not limited to Kerberization,
> Metron-UI, Metron Management UI, or Mpack support), that come in over the
> next 36 hours or so will still be included in the RC.
>
> Does that meet everyone’s needs? I want to get started because it will
> probably take a day or more just to create the branch, an RC build, and
> start the sanity testing.
>
> There’s enough major new stuff here that I’m going to call it 0.4.0. Is
> that also okay with everyone?
>
> Thanks,
> --Matt
>
> On 4/5/17, 6:23 PM, "Ali Nazemian"  wrote:
>
> Dear Metron Devs,
>
> As Metron users/customers, we are very keen to have all high priority
> related features/bugs to the Security as well as Metron-UI and Metron
> Management-UI.
>
> Thanks,
> Ali
>
> On Thu, Apr 6, 2017 at 8:04 AM, Ryan Merriman  wrote:
>
> > We just finished responding to the first round of feedback so I don't
> think
> > we're that far away on METRON-623.
> >
> > On Wed, Apr 5, 2017 at 3:30 PM, Matt Foley  wrote:
> >
> > > Totally agree would be good to have MPack support. Let’s see how it
> > > goes. Wouldn’t want to cut it out for the sake of a day or two.
> > >
> > > On 4/5/17, 1:14 PM, "Justin Leet"  wrote:
> > >
> > > I've made fairly good progress on
> > > https://issues.apache.org/jira/browse/METRON-799 (The MPack should
> > > function
> > > in a kerberized cluster). The PR itself might cut close to the
> > > deadline,
> > > and in particular might be tough to get reviewed in time.
> > >
> > > I'll do a best effort attempt to get it in to make our Kerberos story
> > > more
> > > complete, but I'd say the release can go on without this (and we use
> > > manual
> > > Kerberos in its absence).
> > >
> > > Justin
> > >
> > > On Wed, Apr 5, 2017 at 4:07 PM, Matt Foley  wrote:
> > >
> > > > Sure. To be clear, I wasn’t proposing an exclusive list, just
> > > making the
> > > > argument that there seemed to be enough to proceed with. Any duly
> > > > committed content in the master branch, at the time we create the
> > > first RC
> > > > (ie, some time after METRON-623 goes in, but not before Monday)
> > will
> > > surely
> > > > be included in the RC, unless something has a bug that can’t be
> > > readily
> > > > resolved.
> > > >
> > > > Thanks,
> > > > --Matt
> > > >
> > > > On 4/5/17, 12:56 PM, "David Lyle"  wrote:
> > > >
> > > > I'm working on METRON-826 right now. I'll have a PR up today or
> > > > tomorrow at
> > > > the latest. I'd like to see it go as well.
> > > >
> > > > https://issues.apache.org/jira/browse/METRON-826
> > > >
> > > > -D...
> > > >
> > > >
> > > > On Wed, Apr 5, 2017 at 3:52 PM, Nick Allen  > >
> > > wrote:
> > > >
> > > > > I would like to include #509 with the Fastcapa improvements..
> > > > Already have
> > > > > a +1. I'm just letting it soak giving others some time to
> > > review if
> > > > they
> > > > > feel so inclined.
> > > > >
> > > > > https://github.com/apache/incubator-metron/pull/509
> > > > >
> > > > >
> > > > > On Wed, Apr 5, 2017 at 3:50 PM, James Sirota <
> > > jsir...@apache.org>
> > > > wrote:
> > > > >
> > > > > > I second this. I want to see 623 go in in addition to the
> > > > kerberos work.
> > > > > > When both are in I think it makes sense to do the release
> > > > > >
> > > > > > 04.04.2017, 11:33, "Simon Elliston Ball" <
> > > > si...@simonellistonball.com>:
> > > > > > > I'd really like to see METRON-623 (the ui) get into the
> > > release.
> > > > It
> > > > > > feels like the current PR review is getting close, and that
> > > > getting it in
> > > > > > then focussing on follow on tasks in a separate release
> > > would work
> > > > well.
> > > > > > >
> > > > > > > I would be all for getting a release out if only for the
> > > > Kerberos work.
> > > > > > >
> > > > > > > Simon
> > > > > > >
> > > > > > >> On 4 Apr 2017, at 20:15, zeo...@gmail.com <
> > > zeo...@gmail.com>
> > > > wrote:
> > > > > > >>
> > > > > > >> How far out is the management UI?
> > > > > > >>
> > > > > > >> Jon
> > > > > > >>
> > > > > > >>> On Tue, Apr 4, 2017, 2:09 PM Matt Foley <
> > > ma...@apache.org>
> > > > wrote:
> > > > > > >>>
> > > > > > >>> Hi all,
> > > > > > >>> Although it’s only been a few weeks since the last
> > > release was
> > > > > finally
> > > > > > >>> published, that process started in January :-)
> > > > > > >>> Also, the last commit in 0.3.1 was Feb 23, and there’s
> > > been a
> > > > ton of
> > > > > > >>> really

Re: [DISCUSS] next release proposal

+1


On April 11, 2017 at 13:59:46, Matt Foley (ma...@apache.org) wrote:

Hi all,
Looks to me like the vast majority of the material mentioned below has been
committed. There are still 8 recent PRs that need review and, hopefully,
commit.

I’m going to go ahead and make a release branch, with the understanding
that any further commits (especially but not limited to Kerberization,
Metron-UI, Metron Management UI, or Mpack support), that come in over the
next 36 hours or so will still be included in the RC.

Does that meet everyone’s needs? I want to get started because it will
probably take a day or more just to create the branch, an RC build, and
start the sanity testing.

There’s enough major new stuff here that I’m going to call it 0.4.0. Is
that also okay with everyone?

Thanks,
--Matt

On 4/5/17, 6:23 PM, "Ali Nazemian"  wrote:

Dear Metron Devs,

As Metron users/customers, we are very keen to have all high priority
related features/bugs to the Security as well as Metron-UI and Metron
Management-UI.

Thanks,
Ali

On Thu, Apr 6, 2017 at 8:04 AM, Ryan Merriman  wrote:

> We just finished responding to the first round of feedback so I don't
think
> we're that far away on METRON-623.
>
> On Wed, Apr 5, 2017 at 3:30 PM, Matt Foley  wrote:
>
> > Totally agree would be good to have MPack support. Let’s see how it
> > goes. Wouldn’t want to cut it out for the sake of a day or two.
> >
> > On 4/5/17, 1:14 PM, "Justin Leet"  wrote:
> >
> > I've made fairly good progress on
> > https://issues.apache.org/jira/browse/METRON-799 (The MPack should
> > function
> > in a kerberized cluster). The PR itself might cut close to the
> > deadline,
> > and in particular might be tough to get reviewed in time.
> >
> > I'll do a best effort attempt to get it in to make our Kerberos story
> > more
> > complete, but I'd say the release can go on without this (and we use
> > manual
> > Kerberos in its absence).
> >
> > Justin
> >
> > On Wed, Apr 5, 2017 at 4:07 PM, Matt Foley  wrote:
> >
> > > Sure. To be clear, I wasn’t proposing an exclusive list, just
> > making the
> > > argument that there seemed to be enough to proceed with. Any duly
> > > committed content in the master branch, at the time we create the
> > first RC
> > > (ie, some time after METRON-623 goes in, but not before Monday)
> will
> > surely
> > > be included in the RC, unless something has a bug that can’t be
> > readily
> > > resolved.
> > >
> > > Thanks,
> > > --Matt
> > >
> > > On 4/5/17, 12:56 PM, "David Lyle"  wrote:
> > >
> > > I'm working on METRON-826 right now. I'll have a PR up today or
> > > tomorrow at
> > > the latest. I'd like to see it go as well.
> > >
> > > https://issues.apache.org/jira/browse/METRON-826
> > >
> > > -D...
> > >
> > >
> > > On Wed, Apr 5, 2017 at 3:52 PM, Nick Allen  >
> > wrote:
> > >
> > > > I would like to include #509 with the Fastcapa improvements..
> > > Already have
> > > > a +1. I'm just letting it soak giving others some time to
> > review if
> > > they
> > > > feel so inclined.
> > > >
> > > > https://github.com/apache/incubator-metron/pull/509
> > > >
> > > >
> > > > On Wed, Apr 5, 2017 at 3:50 PM, James Sirota <
> > jsir...@apache.org>
> > > wrote:
> > > >
> > > > > I second this. I want to see 623 go in in addition to the
> > > kerberos work.
> > > > > When both are in I think it makes sense to do the release
> > > > >
> > > > > 04.04.2017, 11:33, "Simon Elliston Ball" <
> > > si...@simonellistonball.com>:
> > > > > > I'd really like to see METRON-623 (the ui) get into the
> > release.
> > > It
> > > > > feels like the current PR review is getting close, and that
> > > getting it in
> > > > > then focussing on follow on tasks in a separate release
> > would work
> > > well.
> > > > > >
> > > > > > I would be all for getting a release out if only for the
> > > Kerberos work.
> > > > > >
> > > > > > Simon
> > > > > >
> > > > > >> On 4 Apr 2017, at 20:15, zeo...@gmail.com <
> > zeo...@gmail.com>
> > > wrote:
> > > > > >>
> > > > > >> How far out is the management UI?
> > > > > >>
> > > > > >> Jon
> > > > > >>
> > > > > >>> On Tue, Apr 4, 2017, 2:09 PM Matt Foley <
> > ma...@apache.org>
> > > wrote:
> > > > > >>>
> > > > > >>> Hi all,
> > > > > >>> Although it’s only been a few weeks since the last
> > release was
> > > > finally
> > > > > >>> published, that process started in January :-)
> > > > > >>> Also, the last commit in 0.3.1 was Feb 23, and there’s
> > been a
> > > ton of
> > > > > >>> really cool new stuff added since then:
> > > > > >>>
> > > > > >>> Biggest items:
> > > > > >>> - Multiple commits for REST API (base Jira:
> METRON-503)
> > > > > >>> - Multiple commits to work with Kerberized (secure)
> > clusters
> > > (mult.
> > > > > Jiras)
> > > > > >>>
> > > > > >>> Other major new features:
> > > > > >>> - METRON-690: DSL-based sparse time window
> >

Re: [DISCUSS] next release proposal

2017-04-11 Thread Matt Foley

Hi all,
Looks to me like the vast majority of the material mentioned below has been 
committed.  There are still 8 recent PRs that need review and, hopefully, 
commit.

I’m going to go ahead and make a release branch, with the understanding that 
any further commits (especially but not limited to Kerberization, Metron-UI, 
Metron Management UI, or Mpack support), that come in over the next 36 hours or 
so will still be included in the RC.

Does that meet everyone’s needs?  I want to get started because it will 
probably take a day or more just to create the branch, an RC build, and start 
the sanity testing.

There’s enough major new stuff here that I’m going to call it 0.4.0.  Is that 
also okay with everyone?

Thanks,
--Matt

On 4/5/17, 6:23 PM, "Ali Nazemian"  wrote:

Dear Metron Devs,

As Metron users/customers, we are very keen to have all high priority
related features/bugs to the Security as well as Metron-UI and Metron
Management-UI.

Thanks,
Ali

On Thu, Apr 6, 2017 at 8:04 AM, Ryan Merriman  wrote:

> We just finished responding to the first round of feedback so I don't 
think
> we're that far away on METRON-623.
>
> On Wed, Apr 5, 2017 at 3:30 PM, Matt Foley  wrote:
>
> > Totally agree would be good to have MPack support.  Let’s see how it
> > goes.  Wouldn’t want to cut it out for the sake of a day or two.
> >
> > On 4/5/17, 1:14 PM, "Justin Leet"  wrote:
> >
> > I've made fairly good progress on
> > https://issues.apache.org/jira/browse/METRON-799 (The MPack should
> > function
> > in a kerberized cluster).  The PR itself might cut close to the
> > deadline,
> > and in particular might be tough to get reviewed in time.
> >
> > I'll do a best effort attempt to get it in to make our Kerberos 
story
> > more
> > complete, but I'd say the release can go on without this (and we use
> > manual
> > Kerberos in its absence).
> >
> > Justin
> >
> > On Wed, Apr 5, 2017 at 4:07 PM, Matt Foley  wrote:
> >
> > > Sure.  To be clear, I wasn’t proposing an exclusive list, just
> > making the
> > > argument that there seemed to be enough to proceed with.  Any duly
> > > committed content in the master branch, at the time we create the
> > first RC
> > > (ie, some time after METRON-623 goes in, but not before Monday)
> will
> > surely
> > > be included in the RC, unless something has a bug that can’t be
> > readily
> > > resolved.
> > >
> > > Thanks,
> > > --Matt
> > >
> > > On 4/5/17, 12:56 PM, "David Lyle"  wrote:
> > >
> > > I'm working on METRON-826 right now. I'll have a PR up today 
or
> > > tomorrow at
> > > the latest. I'd like to see it go as well.
> > >
> > > https://issues.apache.org/jira/browse/METRON-826
> > >
> > > -D...
> > >
> > >
> > > On Wed, Apr 5, 2017 at 3:52 PM, Nick Allen  >
> > wrote:
> > >
> > > > I would like to include #509 with the Fastcapa 
improvements..
> > > Already have
> > > > a +1.  I'm just letting it soak giving others some time to
> > review if
> > > they
> > > > feel so inclined.
> > > >
> > > > https://github.com/apache/incubator-metron/pull/509
> > > >
> > > >
> > > > On Wed, Apr 5, 2017 at 3:50 PM, James Sirota <
> > jsir...@apache.org>
> > > wrote:
> > > >
> > > > > I second this.  I want to see 623 go in in addition to the
> > > kerberos work.
> > > > > When both are in I think it makes sense to do the release
> > > > >
> > > > > 04.04.2017, 11:33, "Simon Elliston Ball" <
> > > si...@simonellistonball.com>:
> > > > > > I'd really like to see METRON-623 (the ui) get into the
> > release.
> > > It
> > > > > feels like the current PR review is getting close, and 
that
> > > getting it in
> > > > > then focussing on follow on tasks in a separate release
> > would work
> > > well.
> > > > > >
> > > > > > I would be all for getting a release out if only for the
> > > Kerberos work.
> > > > > >
> > > > > > Simon
> > > > > >
> > > > > >>  On 4 Apr 2017, at 20:15, zeo...@gmail.com <
> > zeo...@gmail.com>
> > > wrote:
> > > > > >>
> > > > > >>  How far out is the management UI?
> > > > > >>
> > > > > >>  Jon
> >

[GitHub] incubator-metron pull request #516: METRON-830 Adding StringFunctions to Ste...

Github user mattf-horton commented on a diff in the pull request:

https://github.com/apache/incubator-metron/pull/516#discussion_r110964577
  
--- Diff: metron-platform/metron-common/README.md ---
@@ -434,6 +466,14 @@ The `!=` operator is the negation of the above.
 * dateTime - The datetime as a long representing the milliseconds 
since unix epoch
   * Returns: The current month (0-based).
 
+### `PREPEND_IF_MISSING`
+  * Description: Prepends the prefix to the start of the string if the 
string does not already start with any of the prefixes.
+  * Input:
+* string - The string to be prepended.
+* prefix - The string prefix to prepend to the start of the string.
+* prefixes - Optional - Additional string prefixes that are valid.
--- End diff --

ditto


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request #516: METRON-830 Adding StringFunctions to Ste...

Github user mattf-horton commented on a diff in the pull request:

https://github.com/apache/incubator-metron/pull/516#discussion_r110964390
  
--- Diff: metron-platform/metron-common/README.md ---
@@ -167,6 +172,14 @@ The `!=` operator is the negation of the above.
 | [ `WEEK_OF_YEAR`](#week_of_year) 
  |
 | [ `YEAR`](#year) 
  |
 
+### `APPEND_IF_MISSING`
+  * Description: Appends the suffix to the end of the string if the string 
does not already end with any of the suffixes.
+  * Input:
+* string - The string to be appended.
+* suffix - The string suffix to append to the end of the string.
+* suffixes - Optional - Additional string suffixes that are valid 
terminators.
--- End diff --

Please state the format of "suffixes".  Is it a string, a regex, an array 
of strings, or what?  If it is a single string, how does it represent plural 
suffixes?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request #516: METRON-830 Adding StringFunctions to Ste...

Github user mattf-horton commented on a diff in the pull request:

https://github.com/apache/incubator-metron/pull/516#discussion_r110965525
  
--- Diff: 
metron-platform/metron-common/src/main/java/org/apache/metron/common/dsl/functions/StringFunctions.java
 ---
@@ -343,4 +343,89 @@ public Object apply(List args) {
   return String.format(format, formatArgs);
 }
   }
+
+  @Stellar( name="CHOP"
+  , description = "Remove the last character from a String"
+  , params = { "the String to chop last character from, may be 
null"}
+  , returns = "String without last character, null if null String 
input"
+  )
+  public static class chop extends BaseStellarFunction {
+
+@Override
+public Object apply(List strings) {
+
+  if(strings.size() == 0) {
+throw new IllegalArgumentException("[CHOP] missing argument: 
string to be chopped");
--- End diff --

Any thoughts about why treat nulls and empty strings differently?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Discuss] Docker and RPMs and bears Oh My

I did, but I fixed it.  It was something with what I’m adding tot he SPEC


On April 11, 2017 at 12:40:33, David Lyle (dlyle65...@gmail.com) wrote:

Do you have something that introduces an error into the RPM build? I'd like
to catch it and correct it.

-D...


On Tue, Apr 11, 2017 at 11:18 AM, Otto Fowler 
wrote:

> I have created https://issues.apache.org/jira/browse/METRON-843.
>
> Right now, if the RPM phase of the build pipeline fails, maven just plows
> along. I don’t believe this is correct.
> If the RPMs fail, the build should fail ( if it was trying to build rpms
).
>
> So for example, if you do vagrant up in full_dev, but the rpm’s fail to
> build, you won’t fail until installing the enrichment service in ambari (
> because the /localrepo is empty ).
> I am not sure how we address this, but I think it is important that the
> build doesn’t continue in a failed state.
>
> Also,
>
> At one point this workflow worked :
> https://cwiki.apache.org/confluence/display/METRON/
> Metron+Installation+on+an+Ambari-Managed+Cluster
> Using a docker image to build the product, and then being able to deploy
> etc.
> I don’t believe this flow will work now, because the build will try to
run
> docker ( within docker ) to build the RPM’s.
> I am not sure if this is technically true, but I think this is a
> regression. But the ambari/rpm flow is new, so that is OK, if we have a
> plan on
> how we are going to move it forward and iron out the kinks.
>
> Both of these issues are important ( I think ) on their own. Taken
> together, it seems to me that we may want to step back and think about
how
> how we are using docker
> and refactor some of these disparate pieces into a more consistent
> approach.
>
> Thoughts?
>

Re: metron UI

2017-04-11 Thread Ryan Merriman

That PR was merged this morning.  Do a pull and you should see it in master.

On Tue, Apr 11, 2017 at 11:44 AM, moshe jarusalem  wrote:

> Hi All,
> Am I missing something basic ? or something other? Would you promptly
> redirect to a doc ?
>
> On Tue, Apr 11, 2017 at 4:08 PM, moshe jarusalem  wrote:
>
> > Hi All,
> > I am trying to install metron UI mentioned at the following link
> >
> >   https://github.com/apache/incubator-metron/pull/489#
> > discussion_r109166246
> >
> > but the metron-config project is not available at the repository.
> >
> > Regards,
> >
>

Re: [Discuss] Docker and RPMs and bears Oh My

2017-04-11 Thread David Lyle

Do you have something that introduces an error into the RPM build? I'd like
to catch it and correct it.

-D...


On Tue, Apr 11, 2017 at 11:18 AM, Otto Fowler 
wrote:

> I have created https://issues.apache.org/jira/browse/METRON-843.
>
> Right now, if the RPM phase of the build pipeline fails, maven just plows
> along.  I don’t believe this is correct.
> If the RPMs fail, the build should fail ( if it was trying to build rpms ).
>
> So for example, if you do vagrant up in full_dev, but the rpm’s fail to
> build, you won’t fail until installing the enrichment service in ambari (
> because the /localrepo is empty ).
> I am not sure how we address this, but I think it is important that the
> build doesn’t continue in a failed state.
>
> Also,
>
> At one point this workflow worked :
> https://cwiki.apache.org/confluence/display/METRON/
> Metron+Installation+on+an+Ambari-Managed+Cluster
> Using a docker image to build the product, and then being able to deploy
> etc.
> I don’t believe this flow will work now, because the build will try to run
> docker ( within docker ) to build the RPM’s.
> I am not sure if this is technically true, but I think this is a
> regression.  But the ambari/rpm flow is new, so that is OK, if we have a
> plan on
> how we are going to move it forward and iron out the kinks.
>
> Both of these issues are important ( I think ) on their own.  Taken
> together, it seems to me that we may want to step back and think about how
> how we are using docker
> and refactor some of these disparate pieces into a more consistent
> approach.
>
> Thoughts?
>

[Discuss] Docker and RPMs and bears Oh My

I have created https://issues.apache.org/jira/browse/METRON-843.

Right now, if the RPM phase of the build pipeline fails, maven just plows
along.  I don’t believe this is correct.
If the RPMs fail, the build should fail ( if it was trying to build rpms ).

So for example, if you do vagrant up in full_dev, but the rpm’s fail to
build, you won’t fail until installing the enrichment service in ambari (
because the /localrepo is empty ).
I am not sure how we address this, but I think it is important that the
build doesn’t continue in a failed state.

Also,

At one point this workflow worked :
https://cwiki.apache.org/confluence/display/METRON/Metron+Installation+on+an+Ambari-Managed+Cluster
Using a docker image to build the product, and then being able to deploy
etc.
I don’t believe this flow will work now, because the build will try to run
docker ( within docker ) to build the RPM’s.
I am not sure if this is technically true, but I think this is a
regression.  But the ambari/rpm flow is new, so that is OK, if we have a
plan on
how we are going to move it forward and iron out the kinks.

Both of these issues are important ( I think ) on their own.  Taken
together, it seems to me that we may want to step back and think about how
how we are using docker
and refactor some of these disparate pieces into a more consistent approach.

Thoughts?

[GitHub] incubator-metron issue #516: METRON-830 Adding StringFunctions to Stellar - ...

2017-04-11 Thread ottobackwards

Github user ottobackwards commented on the issue:

https://github.com/apache/incubator-metron/pull/516
  
+1, thanks for the contribution


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #500: METRON-795: Install Metron REST with Ambari MPa...

Github user justinleet commented on the issue:

https://github.com/apache/incubator-metron/pull/500
  
"confident this PR", not "confident that".  In retrospect, it sounds like 
I'm referring to your last comment, not just in general.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #500: METRON-795: Install Metron REST with Ambari MPa...

Github user justinleet commented on the issue:

https://github.com/apache/incubator-metron/pull/500
  
@merrimanr I'm pretty confident that is going to collide unpleasantly with 
https://github.com/apache/incubator-metron/pull/518 (The MPack should function 
in a kerberized cluster).

I haven't thought through the details, but do you think it's potentially 
sufficient to make this component optional (cardinality 0+, rather than 1)?  
It's an extra step for the user, but it's only selecting it on the component 
list.  At that point, we say the REST API + UI is only supported on 
non-kerberized clusters (which is true anyway), and we (hopefully) don't break 
Kerberizing the core components.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #518: METRON-799: The MPack should function in a kerb...

Github user justinleet commented on the issue:

https://github.com/apache/incubator-metron/pull/518
  
Full dev is able to successfully startup, be Kerberized via Ambari without 
errors (including Storm service check), and have new data flow through.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #521: METRON-835 Use Profiler with Kerberos

2017-04-11 Thread mmiklavc

Github user mmiklavc commented on the issue:

https://github.com/apache/incubator-metron/pull/521
  
We would normally want to push format changes to a separate PR because it's 
hard to follow what has changed here, but the steps still look consistent to 
me. Were you able to resolve the issues with the Kafka ACLs in the current 
order? I recall from the mailing list there was some issue there and it wasn't 
clear if the user needed to be logged in as 'root' instead of 'metron'.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #521: METRON-835 Use Profiler with Kerberos

2017-04-11 Thread mmiklavc

Github user mmiklavc commented on the issue:

https://github.com/apache/incubator-metron/pull/521
  
You and @JonZeolla are going to collide - 
https://github.com/apache/incubator-metron/pull/510


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #510: METRON-821 Minor fixes in full dev kerberos set...

2017-04-11 Thread mmiklavc

Github user mmiklavc commented on the issue:

https://github.com/apache/incubator-metron/pull/510
  
You and @nickwallen are going to collide - 
https://github.com/apache/incubator-metron/pull/521


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request #489: METRON-623: Management UI

2017-04-11 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-metron/pull/489


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Can't assign and take jira case in progress

2017-04-11 Thread Vladimir Shlyakhtin

Hello,

I found minor bug and opened jira case (METRON-838) but is not able to assign 
it to myself and take in progress.

Is it possible to give me such permission?

Thank you

- Vladimir

[GitHub] incubator-metron issue #516: METRON-830 Adding StringFunctions to Stellar - ...

2017-04-11 Thread cestella

Github user cestella commented on the issue:

https://github.com/apache/incubator-metron/pull/516
  
This looks good to me, anand.  Thanks so much for the contribution.  I'll 
spin it up and try the functions out in a REPL.  @mattf-horton @ottobackwards 
anything other outstanding concerns?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request #519: METRON-832 Fixed CEF parser for Palo Alt...

2017-04-11 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-metron/pull/519


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron issue #518: METRON-799: The MPack should function in a kerb...