Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/949
---
Github user merrimanr closed the pull request at:
https://github.com/apache/metron/pull/957
---
Github user merrimanr closed the pull request at:
https://github.com/apache/metron/pull/945
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/958
# Testing Plan:
We presume
* `ZOOKEEPER` is an environment variable set to the zk quorum (e.g.
`node1:2181`)
* `BROKER` is an environment variable set to the broker (e.g. `node1:6667`)
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/949
+1 thanks!
---
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
+1, I'm able to spin it up and query. Good job!
---
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
Don't leave an extra square brace. Sigh. My bad
---
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
Error code is just a 400, btw.
---
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
I'm unable to get a fairly basic query working. A matching doc exists,
based on querying solr directly. I assume I'm doing something obviously wrong
here?
```
{
"fields": [
GitHub user cestella reopened a pull request:
https://github.com/apache/metron/pull/949
METRON-1471: Migrate shuffle connections to local or shuffle
## Contributor Comments
Currently, we use shuffle groupings when we do not want to group by field.
We should, instead, use local
Github user cestella closed the pull request at:
https://github.com/apache/metron/pull/949
---
GitHub user cestella opened a pull request:
https://github.com/apache/metron/pull/958
METRON-1483: In performance evaluation, generating synthetic load and
monitoring the write throughput of our kafka-to-kafka topologies has required a
lot of custom scripting. We should have a tool tha
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/945
Ok, I'm cool with it. +1 by inspection; great work.
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/949
@merrimanr Ah, I had forgotten to merge in master yesterday afternoon.
There should be no more shuffles in any of the topologies.
---
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
yeah, don't worry about it, it's not important, just a bit odd.
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/957
I've been maintaining this branch for a while and have been merging in
other branches before they were committed to master. I think that's why you
see all these commits. I merged in feature/METRO
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/941
No, that can wait for the follow-on ticket. Could you add a quick
one-sentence blurb about the ElasticsearchTestUtils in the README so things are
easier for anyone to test later (with the knowled
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
There's a bunch of @cestella commits in here. Do you need to merge
feature/METRON-1416-upgrade-solr into this PR?
---
18 matches
Mail list logo
