Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/856
It has been long enough that **I** don't even like this PR any more.
-1
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/980
+1 Thanks @as22323!
---
[
https://issues.apache.org/jira/browse/METRON-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426310#comment-16426310
]
ASF GitHub Bot commented on METRON-1509:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426234#comment-16426234
]
ASF GitHub Bot commented on METRON-1339:
Github user ottobackwards commented on the issue:
Github user lvets commented on the issue:
https://github.com/apache/metron/pull/916
@nickwallen, @ottobackwards , my 0.02$ :)
> For example, with everything in Metron today, you can stand-up a single
node in AWS and use the Mpack to install Metron. It is not as "push button"
[
https://issues.apache.org/jira/browse/METRON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426480#comment-16426480
]
ASF GitHub Bot commented on METRON-1434:
Github user lvets commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426486#comment-16426486
]
ASF GitHub Bot commented on METRON-1510:
GitHub user anandsubbu opened a pull request:
GitHub user anandsubbu opened a pull request:
https://github.com/apache/metron/pull/981
METRON-1510: Update Metron website to include info about github update
subscription
## Contributor Comments
Update to include links for the 'Issues' mailing list. Have also changed
Anand Subramanian created METRON-1510:
-
Summary: Update Metron website to include info about github update
subscription
Key: METRON-1510
URL: https://issues.apache.org/jira/browse/METRON-1510
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425497#comment-16425497
]
ASF GitHub Bot commented on METRON-1507:
GitHub user simonellistonball opened a pull request:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/978
Should this work with ubuntu as well? Would it have to be different? Can
you describe how it works?
---
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425572#comment-16425572
]
ASF GitHub Bot commented on METRON-1507:
Github user ottobackwards commented on the issue:
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/978
The PR includes ubuntu support, the cachier would just cache debs from apt
instead of rpms from yum. TBH I've tested centos more than ubuntu. The use is
still the same though, should be
Simon Elliston Ball created METRON-1507:
---
Summary: Add support for Vagrant Cachier plugin if present
Key: METRON-1507
URL: https://issues.apache.org/jira/browse/METRON-1507
Project: Metron
GitHub user simonellistonball opened a pull request:
https://github.com/apache/metron/pull/978
METRON-1507 Added support for vagrant cachier
## Contributor Comments
This is a Vagrant config change to enable the use of vagrant-cachier to
reduce build times for the full dev
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425576#comment-16425576
]
ASF GitHub Bot commented on METRON-1507:
Github user simonellistonball commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425710#comment-16425710
]
ASF GitHub Bot commented on METRON-1462:
Github user anandsubbu commented on the issue:
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/943
My +1 still holds. Installed both mpacks on a 12-node cluster and was able
to get bro indices to work successfully. Thanks @mmiklavc !
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/978
I didn't think ubuntu had yum repos.d in the image?
---
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425735#comment-16425735
]
ASF GitHub Bot commented on METRON-1507:
Github user ottobackwards commented on the issue:
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/978
The yum stuff only happens in the centos include in ansible, it's not
necessary in the ubuntu version, which uses a different ansible include.
An extra test for the record...
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/943
When I spin this up in Ubuntu, the Indexing topology is unable to write to
Elasticsearch. This may very well be a resource constraint issues in my
environment, but I thought I'd mention it
[
https://issues.apache.org/jira/browse/METRON-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425760#comment-16425760
]
ASF GitHub Bot commented on METRON-1462:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425778#comment-16425778
]
ASF GitHub Bot commented on METRON-1502:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425738#comment-16425738
]
ASF GitHub Bot commented on METRON-1507:
Github user simonellistonball commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/974
Just curious, is there some improved functionality we get out of the newer
Doxia version?
Either way, this gets a +1 from me. I rendered the site book and
everything looks kosher.
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425786#comment-16425786
]
ASF GitHub Bot commented on METRON-1507:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/916
@as22323 Let me first say that this is a nice piece of work. You've
followed all the existing patterns and your contribution looks solid.
But ultimately I am +0 on this. I want others
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/916
Why not add it to /contrib ? Or can we have a way to like to it from docs
or site?
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/687
> @cestella Should we perhaps separate parsing assignments (e.g. move
StellarAssignment.from into the language like you've done here) from actually
updating the variables.
@ottobackwards
[
https://issues.apache.org/jira/browse/METRON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425889#comment-16425889
]
ASF GitHub Bot commented on METRON-1090:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425913#comment-16425913
]
ASF GitHub Bot commented on METRON-1503:
Github user nickwallen commented on the issue:
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/978
Ooops... wrong branch. Let me sort out the PR.
---
[
https://issues.apache.org/jira/browse/METRON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425864#comment-16425864
]
ASF GitHub Bot commented on METRON-1434:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425802#comment-16425802
]
ASF GitHub Bot commented on METRON-1496:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/969
@kevin91nl I think the discussion that you have helped spark here is worthy
of a separate email discuss thread.
This is going to take more thought and discussion in the community to
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425800#comment-16425800
]
ASF GitHub Bot commented on METRON-1507:
Github user simonellistonball commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/943
I was able to replicate this same problem in master running on the ubuntu14
dev environment. This does not seem to be a problem caused by your PR. I will
open a separate defect for this.
[
https://issues.apache.org/jira/browse/METRON-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425870#comment-16425870
]
ASF GitHub Bot commented on METRON-1462:
Github user nickwallen commented on the issue:
Nick Allen created METRON-1508:
--
Summary: Indexing Fails to Write to Elasticsearch
Key: METRON-1508
URL: https://issues.apache.org/jira/browse/METRON-1508
Project: Metron
Issue Type: Bug
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/916
I'd be perfectly happy to reference in Metron docs, external
resources/projects like this that community members might find useful. Good
idea @ottobackwards
---
[
https://issues.apache.org/jira/browse/METRON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425883#comment-16425883
]
ASF GitHub Bot commented on METRON-1434:
Github user nickwallen commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425905#comment-16425905
]
ASF GitHub Bot commented on METRON-1504:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/976
I appreciate the check in the integration test that you added, but can we
add a specific check for this in the unit test; `ParallelEnricherTest`?
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/978
I think this is great. I appreciate that the environments will continue to
work with or without the Cachier plugin installed. Anything we can do to
speed-up the dev environments is a big win in
Github user simonellistonball closed the pull request at:
https://github.com/apache/metron/pull/978
---
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425816#comment-16425816
]
ASF GitHub Bot commented on METRON-1507:
Github user simonellistonball closed the pull request
[
https://issues.apache.org/jira/browse/METRON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425824#comment-16425824
]
ASF GitHub Bot commented on METRON-1507:
GitHub user simonellistonball opened a pull request:
GitHub user simonellistonball opened a pull request:
https://github.com/apache/metron/pull/979
METRON-1507 Added support for vagrant cachier
## Contributor Comments
This is a Vagrant config change to enable the use of vagrant-cachier to
reduce build times for the full dev
[
https://issues.apache.org/jira/browse/METRON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425871#comment-16425871
]
ASF GitHub Bot commented on METRON-1434:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Allen updated METRON-1508:
---
Priority: Minor (was: Critical)
> Indexing Fails to Write to Elasticsearch
>
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425886#comment-16425886
]
ASF GitHub Bot commented on METRON-1367:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/873
IMHO, I just don't see value in capturing timing information like this in
the REPL. Timing information like this would be super valuable when run on a
live cluster in the topologies to help
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/975
Can this fix be tested in a unit or integration test?
---
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425950#comment-16425950
]
ASF GitHub Bot commented on METRON-1367:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425949#comment-16425949
]
ASF GitHub Bot commented on METRON-1462:
Github user mmiklavc commented on the issue:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/943
Awesome, thanks @anandsubbu and @nickwallen!
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/873
I think if you are writing or testing commands in the repl this would be
useful.
If it were moved from stellar to common it could be integrated with the
topologies.
The reason I
[
https://issues.apache.org/jira/browse/METRON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425965#comment-16425965
]
ASF GitHub Bot commented on METRON-1090:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/687
@nickwallen @cestella @mattf-horton , Sorry, I thought that question was
more to @mattf-horton at the time.
@cestella I'm not sure I understand what you are saying. Are you saying
GitHub user as22323 opened a pull request:
https://github.com/apache/metron/pull/980
METRON-1509 Docs - metron-deployment/other-examples - Adding 0.4.1 AWS EC2
Single Node/Vagrant Method
## Contributor Comments
[Please place any comments here. A description of the
[
https://issues.apache.org/jira/browse/METRON-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426147#comment-16426147
]
ASF GitHub Bot commented on METRON-1509:
GitHub user as22323 opened a pull request:
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426096#comment-16426096
]
ASF GitHub Bot commented on METRON-1367:
Github user ottobackwards commented on the issue:
ashah created METRON-1509:
-
Summary: Docs - metron-deployment/other-examples - Adding 0.4.1
AWS EC2 Single Node/Vagrant Method
Key: METRON-1509
URL: https://issues.apache.org/jira/browse/METRON-1509
Project:
[
https://issues.apache.org/jira/browse/METRON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426153#comment-16426153
]
ASF GitHub Bot commented on METRON-1434:
Github user as22323 commented on the issue:
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/873
Did it work out for you to find bottlenecks @ottobackwards ? I would be
more inclined to do multi-run micro-benchmarking (I have a bunch of
multi-sample perfidix runs on all the parser
Github user as22323 commented on the issue:
https://github.com/apache/metron/pull/916
Thanks for the great feedback!
Although I was hoping this would make it into the main build, I understand
what you mean by the "Support Burden".
I found a place in the Metron docs to
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426155#comment-16426155
]
ASF GitHub Bot commented on METRON-1367:
Github user simonellistonball commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426159#comment-16426159
]
ASF GitHub Bot commented on METRON-1449:
Github user nickwallen commented on the issue:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/931
The last two commits are refactorings I performed trying to track down what
I describe in the PR description as a "Known Problem". I need to pull each of
those out as separate PRs.
---
Github user ottobackwards closed the pull request at:
https://github.com/apache/metron/pull/873
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/873
@simonellistonball, i have read and replied to you last about 100 times,
but now I understand. The PR makes it seem like this is a PR for a major
instrumentation/sampling solution, when I
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426180#comment-16426180
]
ASF GitHub Bot commented on METRON-1367:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426185#comment-16426185
]
Otto Fowler commented on METRON-1367:
-
While this is cool IMHO, there doesn't seem to be much support
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/873
I'm shelving this. Thinks for taking a look.
---
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426187#comment-16426187
]
ASF GitHub Bot commented on METRON-1367:
Github user ottobackwards commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/856
This has gone from a small thing to at least 'say' we have a way to check
if we broke all your stellar stuff after upgrade, to stretching it based on
feedback which was a mistake, to a run
[
https://issues.apache.org/jira/browse/METRON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426194#comment-16426194
]
ASF GitHub Bot commented on METRON-1339:
Github user ottobackwards commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426195#comment-16426195
]
ASF GitHub Bot commented on METRON-1339:
Github user ottobackwards closed the pull request at:
Github user ottobackwards closed the pull request at:
https://github.com/apache/metron/pull/856
---
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/873
Well, if it helped, cool, letâs keep it... was just curious about your
use case and whether we should have a bolder scope or if there is anything like
this that would help elsewhere in
[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426199#comment-16426199
]
ASF GitHub Bot commented on METRON-1367:
Github user simonellistonball commented on the issue:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/856
The next attempt at this, if there is one, should start off with some sort
of consensus first. And some agreement on initial scope. This PR would have
been smaller and less ambitious, if that
[
https://issues.apache.org/jira/browse/METRON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426206#comment-16426206
]
ASF GitHub Bot commented on METRON-1339:
Github user ottobackwards commented on the issue:
Github user wardbekker commented on a diff in the pull request:
https://github.com/apache/metron/pull/946#discussion_r179060961
--- Diff:
metron-platform/metron-elasticsearch/src/main/java/org/apache/metron/elasticsearch/utils/ElasticsearchUtils.java
---
@@ -107,32 +113,94 @@
[
https://issues.apache.org/jira/browse/METRON-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425180#comment-16425180
]
ASF GitHub Bot commented on METRON-1465:
Github user wardbekker commented on a diff in the pull
86 matches
Mail list logo
