This looks like it *might* work, but no recording, and 40mins?
https://zoom.us/pricing
On December 11, 2017 at 20:37:00, zeo...@gmail.com (zeo...@gmail.com) wrote:
I think this is a great idea. Hangouts works well but last I checked has a
user # limitation. I don't have any other good
I think this is a great idea. Hangouts works well but last I checked has a
user # limitation. I don't have any other good suggestions, sorry, but I'm
in to attend.
Jon
On Mon, Dec 11, 2017, 16:42 Otto Fowler wrote:
> I think that we all want to have regular community
Hi Michael,
I think you misunderstood my concern. We don't have any problem regarding
the tuning of the indexing topology at this moment. However, based on our
observations, it looks like there is some kind of bug in the indexing
topology about the way it is handling the batch size, so I was
The purpose of this discussion is map out what is required to get the POC
started with https://github.com/apache/metron/pull/858 into master.
The following features were added in the previously mentioned PR:
- Dockerfile for Metron REST
- Dockerfile for Metron UIs
- Docker Compose
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/858#discussion_r156215449
--- Diff: metron-interface/metron-alerts/protractor.conf.js ---
@@ -25,27 +25,28 @@ var SpecReporter =
require('jasmine-spec-reporter').SpecReporter;
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/858#discussion_r156215392
--- Diff:
metron-interface/metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts
---
@@ -58,26 +58,26 @@ describe('metron-alerts
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/858#discussion_r156215355
--- Diff:
metron-interface/metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts
---
@@ -47,7 +47,7 @@ describe('metron-alerts
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/861
Thank you for the contribution @simonellistonball, please be sure to assign
and close METRON-1341 in jira. Cheers! #ynwa
---
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/861
---
I think that we all want to have regular community meetings. We may be
better able to keep to a regular schedule with these meetings if we spread
out the responsibility for them from James and Casey, both of whom have a
lot on their plate already.
I would be willing to coordinate and run the
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/858
I'd actually recommend not using METRON-1344 as the base JIRA. I'd
recommend creating a new JIRA where the requirements for the end-state are laid
out in the description. I'd call this one a PoC
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/861
Yeah, this is good. +1 by inspection.
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/858
I agree with everything that has been said. I will address the minor
changes @cestella suggested and start the discussion thread. Will METRON-1344
work as the base Jira for the feature branch?
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/858
@merrimanr Is it worth having a new discuss thread where you lay out what
you've done, where you expect this to end, and what (if any) work that would be
nice to have but isn't essential for this
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/858
Yep, I think a JIRA for the feature branch and each PR as a subtask is a
good idea.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/858
Similar to https://issues.apache.org/jira/browse/METRON-876
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/858
Maybe a Jira for the feature branch, and each PR as a subtask?
---
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/858#discussion_r156183357
--- Diff: metron-interface/metron-alerts/protractor.conf.js ---
@@ -25,27 +25,28 @@ var SpecReporter =
require('jasmine-spec-reporter').SpecReporter;
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/858#discussion_r156182999
--- Diff:
metron-interface/metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts
---
@@ -47,7 +47,7 @@ describe('metron-alerts
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/858#discussion_r156183048
--- Diff:
metron-interface/metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts
---
@@ -58,26 +58,26 @@ describe('metron-alerts
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/859
**Testing**
Run the EC2 deployment
```
cd metron-deployment/amazon-ec2
./run.sh
```
The dev profile should now be set for the REST API. This is the same way we
spin up
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/859
Just a heads up, I've added the spring profile to the ec2 blueprint.
---
Oops, sorry, I kept working on it ¯\_(ツ)_/¯
On December 11, 2017 at 12:58:28, Laurens Vets (laur...@daemon.be) wrote:
On 2017-12-11 06:18, Otto Fowler wrote:
> I have written a script:
>
https://github.com/ottobackwards/Metron-and-Nifi-Scripts/blob/master/metron/metron-rc-check.sh
> .
> I think
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/857
I've hit the same intermittent errors trying this, e.g.
```
[INFO] - Failed: unknown error: Element ... is not clickable at point
(1279, 95). Other element would receive the
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/858
I think getting the feature branch set up was a great first step, so thanks
for setting that up, @merrimanr.
I agree with @ottobackwards, that we need a discussion on what the next
steps
Note: currently the rat check on RC1 doesn’t work, so the build will fail.
I still have some work to do for catching errors.
On December 11, 2017 at 09:18:00, Otto Fowler (ottobackwa...@gmail.com)
wrote:
I have written a script:
I have written a script:
https://github.com/ottobackwards/Metron-and-Nifi-Scripts/blob/master/metron/metron-rc-check.sh
.
I think it might be useful. If any of you could give it a look over and
perhaps try it, I would appreciate it.
GitHub user MohanDV opened a pull request:
https://github.com/apache/metron/pull/862
METRON-1343: Swagger UI for User Controller needs request method
## Contributor Comments
Swagger UI for metron rest endpoints for User Controller has multiple
requestMethods listed for the
28 matches
Mail list logo