[
https://issues.apache.org/jira/browse/EAGLE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-162.
---
Resolution: Fixed
Fix Version/s: v0.3.0
> incomplete class path fails launching Eagle DAM HDFS i
[
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-61.
--
Resolution: Fixed
Fix Version/s: v0.3.0
> Support for secured cluster connection & enable Ldap auth
[
https://issues.apache.org/jira/browse/EAGLE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179500#comment-15179500
]
Zhao, Qingwen commented on EAGLE-162:
-
Fixed the bug with https://github.com/apache/inc
[
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179499#comment-15179499
]
ASF GitHub Bot commented on EAGLE-61:
-
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-eagle/pull/111
---
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 featur
Github user RalphSu commented on the pull request:
https://github.com/apache/incubator-eagle/pull/109#issuecomment-192119175
Looks good to me.
+1
@qingwen220 please help review as well.
---
If your project is set up for it, you can reply to this email and have your
reply app
[
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179378#comment-15179378
]
ASF GitHub Bot commented on EAGLE-61:
-
Github user RalphSu commented on the pull request
Github user RalphSu commented on the pull request:
https://github.com/apache/incubator-eagle/pull/111#issuecomment-192118955
Looks good to me.
+1
---
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 no
Github user senthilec566 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/109#issuecomment-192117041
@qingwen220 Repaced dataSource with application field.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
[
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179268#comment-15179268
]
ASF GitHub Bot commented on EAGLE-61:
-
GitHub user qingwen220 opened a pull request:
GitHub user qingwen220 opened a pull request:
https://github.com/apache/incubator-eagle/pull/111
EAGLE-61 classification supports secured cluster connection & enable Ldap
authentication
https://issues.apache.org/jira/browse/EAGLE-61
You can merge this pull request into a Git repos
[
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-61:
---
Summary: Support for secured cluster connection & enable Ldap
authentication (was: HDFS classification
Github user qingwen220 closed the pull request at:
https://github.com/apache/incubator-eagle/pull/104
---
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 fe
[
https://issues.apache.org/jira/browse/EAGLE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179266#comment-15179266
]
ASF GitHub Bot commented on EAGLE-162:
--
Github user qingwen220 closed the pull request
We can skip Hadoop/storm related dependency but need test how to run
within sandbox.
Thanks
Edward
On 3/3/16, 19:12, "Dendukuri, Hemanth" wrote:
>I got this comment for infrastructure bug.
>
>That's your problem: we have upload limits in place that defaults to
>200MB.
>
>
>
>On 3/3/16, 4:56 PM
I got this comment for infrastructure bug.
That's your problem: we have upload limits in place that defaults to 200MB.
On 3/3/16, 4:56 PM, "Dendukuri, Hemanth" wrote:
>Hi All,
>
>I am not abel to commit eagle release artifact to
>https://dist.apache.org/repos/dist/dev/incubator/eagle/
>
>T
[
https://issues.apache.org/jira/browse/EAGLE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jilin, Jiang resolved EAGLE-157.
Resolution: Fixed
> policy metric should be refreshed every minute
>
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-eagle/pull/110
---
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 featur
Github user qingwen220 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/110#issuecomment-192071973
LGTM +1
---
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 fe
GitHub user zombieJ opened a pull request:
https://github.com/apache/incubator-eagle/pull/110
Eagle 157 policy metric should be refreshed every minute
add refresh interval
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zombieJ/in
Hi All,
I am not abel to commit eagle release artifact to
https://dist.apache.org/repos/dist/dev/incubator/eagle/
The artifact I am trying to commit is 363 MB in size.
Error message :
svn commit apache-eagle-0.3.0-incubating-bin.tar.gz -m "Eagle Incubating
Release 0.3.0 main Artifact"
Adding (
Hao Chen created EAGLE-184:
--
Summary: Migrate eagle website from
https://github.com/eaglemonitoring/eaglemonitoring.github.io to document branch
Key: EAGLE-184
URL: https://issues.apache.org/jira/browse/EAGLE-184
[
https://issues.apache.org/jira/browse/EAGLE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178164#comment-15178164
]
ASF GitHub Bot commented on EAGLE-177:
--
Github user haoch commented on the pull reques
Github user haoch commented on the pull request:
https://github.com/apache/incubator-eagle/pull/108#issuecomment-191866196
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
en
[
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177719#comment-15177719
]
ASF GitHub Bot commented on EAGLE-61:
-
Github user qingwen220 closed the pull request at
Github user qingwen220 closed the pull request at:
https://github.com/apache/incubator-eagle/pull/99
---
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 fea
[
https://issues.apache.org/jira/browse/EAGLE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-183.
---
Resolution: Fixed
Fix Version/s: v0.3.0
Fixed with Ticket EAGLE-177
> Replace Legacy "dataSourc
[
https://issues.apache.org/jira/browse/EAGLE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-177.
---
Resolution: Fixed
Fix Version/s: v0.3.0
> Replace Legacy "dataSource" field with "application" i
GitHub user senthilec566 opened a pull request:
https://github.com/apache/incubator-eagle/pull/109
Added RM Policy and GC Policies in Resource
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/senthilec566/incubator-eagle EAGLE-180
[
https://issues.apache.org/jira/browse/EAGLE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177582#comment-15177582
]
ASF GitHub Bot commented on EAGLE-177:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-eagle/pull/108
---
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 featur
[
https://issues.apache.org/jira/browse/EAGLE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177570#comment-15177570
]
ASF GitHub Bot commented on EAGLE-177:
--
Github user RalphSu commented on the pull requ
Github user RalphSu commented on the pull request:
https://github.com/apache/incubator-eagle/pull/108#issuecomment-191681816
+1
Unit runs ok for me.
Be careful this would be incompatible for existing deployment if one
already deployed. The one who already load the format of o
[
https://issues.apache.org/jira/browse/EAGLE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177494#comment-15177494
]
ASF GitHub Bot commented on EAGLE-177:
--
GitHub user qingwen220 opened a pull request:
GitHub user qingwen220 opened a pull request:
https://github.com/apache/incubator-eagle/pull/108
EAGLE-177 Replace Legacy "dataSource" field with "application" in all
metadata
https://issues.apache.org/jira/browse/EAGLE-177
You can merge this pull request into a Git repository by r
35 matches
Mail list logo