Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/929
+1
---
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/932
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/929
Yes I pushed the change to zookeeper with Swagger. Probably just a minor
detail he missed in his instructions.
You can use either "localhost:9983" or "node1:9983". That address is the
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/929
@merrimanr did you push the configs to zookeeper?
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/929
+1 from me pending approval from others. Tested this in full dev and
worked fine.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/929
Everything worked, just wondering about the questions above before I check
off.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/929
don't we have to push the new config to zookeeper?
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/929
Why is it "solr.zookeeper" : "localhost:9983" and not solr.ip?
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/929
Ok, I wrote up a detailed testing plan to get this running in full-dev. I
want to add a couple of unit tests around the new properties that I added, but
at that point, this is feature complete and
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/928
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/930
+1 Thanks @wardbekker !
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/932
+1 Works great. This was an annoying one to track down. Great detective
work @anandsubbu
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/932
I spun this up and I know longer see the Indexing component as red. +1 as
soon as @nickwallen's build finishes and it's working there too.
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/932
Thanks @anandsubbu . This looks like a solid fix. Spinning it up now.
---
GitHub user anandsubbu reopened a pull request:
https://github.com/apache/metron/pull/932
METRON-1451: On Centos full dev, Metron Indexing shows up as stopped
## Contributor Comments
**Root Cause**
The python-requests module introduced a VendorAlias import machinery in
Github user anandsubbu closed the pull request at:
https://github.com/apache/metron/pull/932
---
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/895
Ok, so we have some authentication, with clear text passwords, but we don't
have any authorization on the end points, which causes compliance issues with
things like access change request.
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/895
-1 (non-binding) This is a pen-tester's dream. We currently have no
authentication around this endpoint, and allowing it to actually set acls make
it a serious security hole. That may be
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/922
@cestella much neater. Thank you! I'll put my data schema OCD away now.
---
Github user simonellistonball commented on a diff in the pull request:
https://github.com/apache/metron/pull/922#discussion_r166908797
--- Diff:
metron-platform/metron-solr/src/main/config/schema/error/solrconfig.xml ---
@@ -0,0 +1,1601 @@
+
--- End diff --
Is
Github user MohanDV commented on the issue:
https://github.com/apache/metron/pull/895
Bump. Can anyone offer a binding +1 ? I Would like to get this in.
---
GitHub user anandsubbu opened a pull request:
https://github.com/apache/metron/pull/932
METRON-1451: On Centos full dev, Metron Indexing shows up as stopped
## Contributor Comments
**Root Cause**
The python-requests module introduced a VendorAlias import machinery in
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/914
My bad: the dependencies file is updated, but not the NOTICES.
---
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/914
And in fairness to you, we don't do the NOTICES properly for anything else
either I see. That's probably a separate scope.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/914
Um, it is updated.
---
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/914
And in more topical an relevant points... we're introducing a net new
dependency here... Do we need to also update the NOTICES file (and the
dependencies_with_url.csv list)?
---
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/914
@ottobackwards Really want that myth to be a reality... as soon as we can
get the config overwrite problem solved... but this really isn't the ticket to
discuss that on :)
I'm
27 matches
Mail list logo
