[GitHub] metron pull request #731: METRON-1146 Refactor for ParserExtensionConfig and...

2017-09-02 Thread ottobackwards 
GitHub user ottobackwards opened a pull request:

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

METRON-1146  Refactor for ParserExtensionConfig and Rest get all call

This a PR for some cleanup on the 1136 Feature Branch

- return a list from GET ( getAllParsers ) and not a map.
- fix names in Parser Extension Configs to be consistant with 
extension/extensions
- add a field just called identifier, to be used instead of assembly name
- differentiate identifier/assemblyname

## 
- [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 ensured that the full suite of tests and checks have been 
executed in the root metron 
- [x] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [x] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?


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

$ git pull https://github.com/ottobackwards/metron ext-refactor-names-getall

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

https://github.com/apache/metron/pull/731.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 #731


commit 0d3b4c01fa41a3ee888a4debf249e62f82f2a184
Author: Otto Fowler 
Date:   2017-09-03T03:17:46Z

Refactor:

- return a list from GET ( getAllParsers ) and not a map.
- fix names in Parser Extension Configs to be consistant with 
extension/extensions
- add a field just called identifier, to be used instead of assembly name
- differentiate identifier/assemblyname




---
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] metron issue #729: METRON-1150: REST parseMessage endpoint fails with Unable...

2017-09-02 Thread ottobackwards 
Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/729
  
Now that there is a feature branch there should be.

This is the commit that has grok working with hdfs, obviously based on 777.


https://github.com/ottobackwards/metron/commit/f0923a6ca4ca0cbfa5fe541311ebe20126a28bad



---
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] Metron release 0.4.1

2017-09-02 Thread Anand Subramanian 
Hello Matt,

Simon's pull request supersedes mine (METRON-1139 / 
https://github.com/apache/metron/pull/722) and is already merged into master. 

Thanks,
Anand



On 9/1/17, 12:41 AM, "Matt Foley"  wrote:

>Please mark them 0.4.1, as that’s what the community says we want to call the 
>upcoming release, and everything that’s there when I throw the switch will be 
>included.
>
>Jon and Anand, will they be in by end/day Friday?
>Thanks,
>--Matt
>
>On 8/31/17, 7:45 AM, "Nick Allen"  wrote:
>
>Matt, et al - For JIRAs that are going into master, should we be marking
>these as "Next + 1" or "0.4.1" ?
>
>On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com  wrote:
>
>> Can I advocate to get METRON-1129 in the RC, and throw in a second vote 
> for
>> METRON-1134?  Both in an attempt to better support of prod/offline use.
>> Happy to provide testing cycles for the former.
>>
>> Jon
>>
>> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
>> asubraman...@hortonworks.com> wrote:
>>
>> > Hi Matt,
>> >
>> > This defect needs to be included as a follow-on to METRON-1122:
>> > * METRON-1141 (https://github.com/apache/metron/pull/723)
>> >
>> >
>> > Thanks,
>> > Anand
>> >
>> >
>> >
>> > On 8/30/17, 8:57 PM, "Michael Miklavcic" 
>> > wrote:
>> >
>> > >I have some work around fixing how we handle config with Ambari that 
> I'd
>> > >like to see go in. No PR yet, but coming soon. I expect to have this 
> by
>> > the
>> > >RC deadline.
>> > >
>> > >Mike
>> > >
>> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen  
> wrote:
>> > >
>> > >> The following PRs are usability enhancements for the Profiler.  They
>> are
>> > >> fairly simple and I think are very helpful for troubleshooting.  I
>> don't
>> > >> want to hold up the release, but it would be a "nice to have" to get
>> > these
>> > >> in.
>> > >>
>> > >> If anyone has cycles, I would appreciate some reviews of these PRs.
>> > >> https://github.com/apache/metron/pull/721
>> > >> https://github.com/apache/metron/pull/716
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:
>> > >>
>> > >> > Okay, just to be clear, you’re requesting we wait until Friday, if
>> > >> > necessary, to cut an RC with 717 in it?
>> > >> > Thanks,
>> > >> > --Matt
>> > >> >
>> > >> > On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
>> > >> >
>> > >> > 709 is in and 717 is under concerted review by Otto.  I'd like
>> to
>> > see
>> > >> > it in
>> > >> > by Friday.
>> > >> >
>> > >> > On Tue, Aug 29, 2017 at 1:35 PM, Matt Foley 
>> > >> wrote:
>> > >> >
>> > >> > > Hi all,
>> > >> > > Thanks for your inputs.  The three PRs Nick mentioned have
>> been
>> > >> > > successfully closed.
>> > >> > > Casey, do you have an ETA for these two PRs? (PR#709 and 
> 717)
>> > >> > > Thanks,
>> > >> > > --Matt
>> > >> > >
>> > >> > > On 8/29/17, 9:34 AM, "Casey Stella" 
>> wrote:
>> > >> > >
>> > >> > > For my PRs, I'd vote for METRON-1122 being in (commit 
> very
>> > >> > imminent).
>> > >> > > I'd very much like METRON-1134 to be in as well.
>> > >> > >
>> > >> > > Beyond that, I'm ok
>> > >> > >
>> > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
>> > >> n...@nickallen.org>
>> > >> > > wrote:
>> > >> > >
>> > >> > > > Thanks for starting the process, Matt.
>> > >> > > >
>> > >> > > > These are my own open PRs that I would most like to 
> see
>> > get
>> > >> in.
>> > >> > > They all
>> > >> > > > relate to the Profiler. My other outstanding PRs are
>> less
>> > >> > important.
>> > >> > > >
>> > >> > > >- https://github.com/apache/metron/pull/705
>> > >> > > >- https://github.com/apache/metron/pull/707
>> > >> > > >- https://github.com/apache/metron/pull/708
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <
>> > ma...@apache.org
>> > >> >
>> > >> > wrote:
>> > >> > > >
>> > >> > > > > Hello all,
>> > >> > > > > At the meeting this morning, the community expressed
>> the
>> > >> > wish to
>> > >> > > create a
>> > >> > > > > new release, to be a point release and not including
>> > >> > METRON-777.
>> > >> > > > >
>> > >> > > > > Therefore, I propose to create release 0.4.1 from
>> Metron
>> > >> > master
>> > >> > > branch,
>> > >> >