GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/993
update for compatibiliy to python3
- used requests instead of urllib
- updated print statements
- used input instead of raw_input
Be sure to do all of the following to help us
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/992
why this was closed and not merged?
---
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/975#discussion_r199368279
--- Diff: get-started-with-docker.md ---
@@ -32,4 +38,4 @@ Another way to get started with Apache Eagle (called
Eagle in the following
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/992
update for compatibiliy to python3
- used requests instead of urllib
- updated print statements
- used input instead of raw_input
You can merge this pull request into a Git repository
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/985
+1
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/986
+1, Thanks
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/987
+1
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/941
Thanks @rushikesavareddy for the PR and @coheigea for verifying. merging it
now.
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/978
+1, merging since its improved than earlier and more improvements can be
later. Thanks for the PR.
---
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/978#discussion_r165162632
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertFilePublisher.java
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/980
+1, merging.. Thanks for the PR.
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/979
+1, merging.. Thanks!
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/941
@rushikesavareddy , can u pls rebase this from master, i think that will
resolve the issue of having other non-relevant commits, pls also take care of
code formatting.
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/972
pls update the PR as per the format, pls refer other closed PRs.
- update description
- add [EAGLE-*] in title
Thanks
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/970
@yizt , can u please describe and create an issue on jira ?
that way it would help to review this PR. Thanks
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/876
@r7raul1984 can you provide more info or status on this PR? is there a plan
to get this platform update into Apache Eagle ? it would be awesome btw. thanks
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/876
Hi @r7raul1984 , do you have any update for this PR ?
---
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
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/968
[EAGLE-973] removing incubating from docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jhsenjaliya/eagle EAGLE-973
Alternatively you can
Github user jhsenjaliya closed the pull request at:
https://github.com/apache/eagle/pull/966
---
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 feature
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/966
[EAGLE-1060] updating version to 0.5.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jhsenjaliya/eagle EAGLE-1060
Alternatively you can
Github user jhsenjaliya closed the pull request at:
https://github.com/apache/eagle/pull/964
---
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 feature
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/964
adding missing apache license header
this is minor fix that adds apache license header to the following file
You can merge this pull request into a Git repository by running:
$ git pull
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/647
I spent lot of time in rebasing this, but eventually it got very confusing
since there are lot of files ( ~1500) to be rebased, which i did
(jhsenjaliya:EAGLE-740-rebased) but there are multiple
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/941
@rushikesavareddy pls make sure this PR passes with checkStyle flag ON.
Also you can make the target branch to master to trigger the CI check and I
will pick it for branch-0.5. Thanks
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/943
@asdf2014 i know how it feels.
but as @qingwen220 pointed out, it will be too much work to make this
compatible for people already running on branch 0.5
how about we take up this on next
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r120473246
--- Diff:
eagle-core/eagle-common/src/main/java/org/apache/eagle/common/mail/EagleMailClient.java
---
@@ -53,16 +53,18 @@ public EagleMailClient(final
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r120473184
--- Diff:
eagle-core/eagle-common/src/main/java/org/apache/eagle/common/mail/EagleMailClient.java
---
@@ -53,16 +53,18 @@ public EagleMailClient(final
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r120471741
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r120471811
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r119933968
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r119933990
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/941#discussion_r119687625
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/email/EagleMailClient.java
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/647
Hi @koone, This would be good to add in 0.5 branch, would you have time to
rebase this and address comments from @haoch ? Thanks
---
If your project is set up for it, you can reply
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/935
@qingwen220 can you please list out some things about the changes, whether
its simply refactoring or adding minor feature ?
---
If your project is set up for it, you can reply to this email
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/937
Thanks @qingwen220, i have merged this into 0.5 branch
---
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
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/936
[EAGLE-1025] bumping version to 0.6 for master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jhsenjaliya/eagle master-version-bump
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/799
@haoch , i think this would be very good feature to have in 0.5, what do
you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/925
@asdf2014 Thanks again, lets work on this after 0.5
---
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
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/925#discussion_r114253159
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertPublisherImpl.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/925#discussion_r114253102
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertEagleStorePlugin.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/925#discussion_r114252915
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert-service/src/main/java/org/apache/eagle/service/alert/resolver/AttributeResolverFactory.java
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/929
@vikash0837 please close this PR, and send email to d...@eagle.apache.org
---
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
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/927
+1, LGTM
---
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
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/929
@vikash0837 please create jira bug issue for this ( ex:
https://issues.apache.org/jira/browse/EAGLE-925 )
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/914
@qinzhaokun, @haoch can u please review this ? its working fine now
---
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
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/926#discussion_r112627380
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertEmailPublisher.java
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/926#discussion_r112565522
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/publisher/impl/AlertEmailPublisher.java
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/919
@qingwen220, looks like this PR needs to be rebased ( since u created it
from ur other branch )
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/905
@asdf2014 please add [MINOR] tag in pr title since there is not jira for
this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/916
This was merged with master, will rebase branch-0.5 or cherry pick this
later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jhsenjaliya closed the pull request at:
https://github.com/apache/eagle/pull/916
---
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 feature
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/897
@asdf2014 please squash the commits again and I should merge this.
---
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
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/908#discussion_r111810600
--- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh ---
@@ -0,0 +1,135 @@
+#!/bin/bash
--- End diff --
while packaging this module
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/897
@asdf2014 , can u please squash the commits ?
---
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
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/908
was just going through some PRs, so put some comments...pls take a look.
---
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
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/908#discussion_r111720746
--- Diff: eagle-external/eagle-cdh/src/aux/eagle-server.sh ---
@@ -0,0 +1,135 @@
+#!/bin/bash
--- End diff --
same with server.yml
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/647
@haoch , do you need any help on reviewing this?
@koone, Can you please rebase this PR ? Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/916
[MINOR] adding myself in developer list as a first commit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jhsenjaliya/eagle add-me
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/902
@qingwen220 , @r7raul1984 looks like we can accommodate hbase 1.2.5 with or
without this PR changes but I havent tested with hbase coprocessor enabled. so
if someone can test current eagle code
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/902
@tedyu I pulled your PR and used ur code to run my eagle, I am running
alert engine app + hdfs audit log app and it successfully created the alert i
was expecting. so this PR is working fine
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/914
Docker updates for eagle 0.5
This docker image is for eagle 0.5
There is still an issue where namenode process dies sometimes.
creating this PR to get the review started
You
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/902
master works fine with hbase 1.2.2
I am planning to test this patch with hbase 1.2.5 tonight
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/902
Hi @qingwen220 no, since there are some function signature changes here, I
dont think it will be compatible. ( without those changes, it is compatible
though) so the question really comes down
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/902
+1, LGTM, I will be testing this on my dev environment as well sometime
tomorrow.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/812
i will update this PR with storm 1.1.0 and rebase it after 0.5 release.
---
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
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/849
@haoch, can u please help reviewing this ?
---
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
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/812
i havent explicitly tested it, but from their
[docs](http://storm.apache.org/releases/1.0.2/storm-kafka.html), it looks
compatible with kafka 0.8.1.1 which is used in the example given
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/811
[EAGLE-870] adding required packages into storm-jar
without these required packages, it throws class not found exception, more
detail is in the ticket.
You can merge this pull request
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/777
[EAGLE-865] correcting logger class for MapRFSAuditLogParserBolt.java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jhsenjaliya/eagle
Github user jhsenjaliya commented on a diff in the pull request:
https://github.com/apache/eagle/pull/763#discussion_r94525925
--- Diff: eagle-external/hadoop_jmx_collector/system_metric_collector.py ---
@@ -0,0 +1,300 @@
+# !/usr/bin/python
+#
+# Licensed to the Apache
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/757
@haoch, found 1 last reference in LICENSE file having text like "Apache
Eagle (incubating) Subcomponents:" , otherwise looks good.
---
If your project is set up for it, you
71 matches
Mail list logo
