Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/393
@merrimanr Thanks for pointing out the location of the storm logs. I think
it would be worth adding that to the README.
I have a fix for the kafkazk image running on local
Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/409
@justinleet Good catch. Updated the README to remove the note about Docker
for Mac.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
+1 (non-binding)
On Thu, Jan 5, 2017, 8:30 PM Matt Foley wrote:
> +1 (non-binding)
>
> One typo is still in there:
> >>After discussion of the issue on the JIRA if it is clear that you
> found a bug then you should file a JIRA
> should be
> >>After discussion of the
+1 (non-binding)
One typo is still in there:
>>After discussion of the issue on the JIRA if it is clear that you found
>> a bug then you should file a JIRA
should be
>>After discussion of the issue on the mailing list if it is clear that you
>> found a bug then you should file a JIRA
I'll give it a shot thx!
Regards,
Tyler Moore
Software Engineer
Phone: 248-909-2769
Email: moore.ty...@goflyball.com
On Thu, Jan 5, 2017 at 5:21 PM, Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> Hey Tyler,
>
> Build Metron with the HDP profile to get the proper deps for this
>
Hey all,
Wondering if there is a solution to the "Offset lags for kafka not
supported for older versions. Please update kafka spout to latest version."
error seen when upgrading to metron 0.3.0?
I know it is due to kafka-storm dependency that needs updated, but what is
the best way to go about
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/410
---
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
I attached a sample function to the Jira, just calls a script from on the
server by passing in the path. Certainly could use some work, but I wanted
to make sure this was the right idea and get a consensus, let me know your
thoughts.
My thought process for this is that if we only allow script
Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/400
Jumping in a bit late here.
Please take a look at [my
PR](https://github.com/anandsubbu/incubator-metron/pull/1) for a suggested
improvement. Tested it on CentOS 6.8 and Mac
Github user jjmeyer0 commented on the issue:
https://github.com/apache/incubator-metron/pull/316
**Project Structure:**
Personally I think the module, `metron-interface`, should be split up into
more modules. I think there should be `metron-rest` and
Hi James -
This looks pretty good!
A couple quick comments:
* for step 10 - the KEYS file appears to be provided for each release as
part of the release candidate itself. While I do see some projects do this,
I think it is actually best practice to have a single KEYS file in a well
known place
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/410
+1, was able to have it spin up and run without issue. Thanks for grabbing
this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user anandsubbu commented on the issue:
https://github.com/apache/incubator-metron/pull/400
Thanks a bunch @mattf-horton for the suggestion. I have now changes the
commands based on sysctl on Mac and meminfo/cpuinfo on Linux.
---
If your project is set up for it, you can
13 matches
Mail list logo