[jira] [Updated] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-78:
--
Description: 
Error under MacOSX

{code}
$ source eagle-external/eagle-docker/bin/eagle-lib.sh
-sh: `run-command': not a valid identifier
-sh: `amb-clean': not a valid identifier
-sh: `get-ambari-server-ip': not a valid identifier
-sh: `get-host-ip': not a valid identifier
-sh: `amb-members': not a valid identifier
-sh: `amb-settings': not a valid identifier
-sh: `docker-ps': not a valid identifier
-sh: `docker-psa': not a valid identifier
-sh: `amb-start-cluster': not a valid identifier
-sh: `amb-shell': not a valid identifier
-sh: `eagle-deploy-cluster': not a valid identifier
-sh: `amb-start-first': not a valid identifier
-sh: `amb-copy-to-hdfs': not a valid identifier
-sh: `amb-create-hdfs-dir': not a valid identifier
-sh: `amb-scp-to-first': not a valid identifier
-sh: `amb-start-node': not a valid identifier
{code}

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS] Provide analytic DSL support

[Liangfei.Su]

No UI design yet.
I'm using EAGLE-79  to
catch the support of stream analyze in eagle framework. UI to be separate
task.
Persist not in this jira either since it could be a parallel task.
On declarative persist, my consideration of persist is through metadata
definition of data source, and schema information. These metadatas should
be able to be update/reload in the similar way of policy lifecycle:

1. User change the metadata defintion
2. The persist executor would periodically reload the metadata from
underlying store. Use latest metadata it read.

Can you elaborate declarative persist? What's the user interface look like
and life cycle management for it?

Ralph


On Tue, Dec 15, 2015 at 3:52 PM, Zhang, Edward (GDI Hadoop) <
yonzh...@ebay.com> wrote:

> We probably also need support declarative persist along with this feature,
> I think.
>
> Is UI design started?
>
> Thanks
> Edward
>
> On 12/14/15, 23:34, "Liangfei.Su"  wrote:
>
> >q1. Yes, same mechanism like policy definition would be used. User would
> >be
> >able to define an analyze-policy, and when analyze executor would try to
> >load and execute the policy. More, in programming, user could simply input
> >their analyze sql directly through API for simplicity.
> >
> >q2. Sure, user would be able to define simple analyze.
> >
> >q3. No, but there are dependency since Hao's work impact the API a lot.
> >pull 26 would quickly decouple this dependency.
> >
> >Ralph
> >
> >
> >On Mon, Dec 14, 2015 at 12:44 PM, Zhang, Edward (GDI Hadoop) <
> >yonzh...@ebay.com> wrote:
> >
> >> Thanks for updating.
> >> Some questions:
> >> 1. do we need aggregator declaration to downloaded from eagle service?
> >>(I
> >> believe it can be used in code directly) If that is true, can we use the
> >> same mechanism for policy lifecycle management? and do we want this
> >> declaration can be updated dynamically?
> >> 2. because aggregator declaration can be expressed with limited syntax,
> >> group by/max/top/avg/Š, is that possible future UI part can be more
> >> intuitive than current policy UI? :-)
> >> 3. How this design is aligned to general purpose monitoring design which
> >> Hao/Chen is working on. I mean in terms of input/output and business
> >> logic, will that be reused in the future?
> >>
> >> Those questions are not urgent request, but we can think of that while
> >> implementing.
> >>
> >> Thanks
> >> Edward
> >>
> >>
> >> On 12/13/15, 18:58, "Liangfei.Su"  wrote:
> >>
> >> >Had a draft spec at
> >> >https://cwiki.apache.org/confluence/display/EAG/Stream+Analyze
> >> >
> >> >Please suggest.
> >> >
> >> >
> >> >Thanks,
> >> >Ralph
> >> >
> >> >
> >> >On Mon, Dec 7, 2015 at 6:00 PM, Liangfei.Su 
> >>wrote:
> >> >
> >> >> For #1, the eagle programming API is mostly sit at the same place of
> >> >> Trident. Besides the platform independence and type safe, the eagle
> >>CEP
> >> >> could be used to help reduce the code effort to submit a topology.
> >>This
> >> >> extend the current alerting define experience to more wise cases.
> >> >>
> >> >> Like
> >> >> trident style of join
> >> >>
> >> >> topology.join(stream1, new Fields("key"), stream2, new Fields("x"),
> >>new
> >> >>Fields("key", "a", "b", "c"));
> >> >>
> >> >>
> >> >> to sql like
> >> >> from stream1=.., stream2=...
> >> >> select stream1.key, stream2.a, stream2.b, stream3.c where
> >> >> stream1.key=stream2.x
> >> >>
> >> >> from windowed join, things could be more complicated, and trident
> >> >>require
> >> >> user to do a couple of persiste/stateQuery by their code.
> >> >>
> >> >> Thanks,
> >> >> Ralph
> >> >>
> >> >> On Mon, Dec 7, 2015 at 5:16 PM, Chen, Hao 
> wrote:
> >> >>
> >> >>> 1. Are you guys re-implement part of Trident?
> >> >>> >> 1) Trident is high-level API but field-based, eagle is
> >> >>>type-oritended.
> >> >>> >> 2) Eagle datastream is platform-indepent, not only on storm
> >> >>> >> 3) Eagle datastream support CEP CQL except for programming API.
> >> >>>
> >> >>> 2. How can the type information kept during the data processing by
> >> >>>Storm?
> >> >>> >> Type information is provided by Scala TypeTag[T]
> >> >>> >> Eagle could serialize valuable type information like type class,
> >> >>>type
> >> >>> fields and so on from TypeTag[T] before submitting to execution
> >> >>>environment
> >> >>> and then shared between processing element like spout/bolt.
> >> >>>
> >> >>>
> >> >>> Thanks,
> >> >>> Hao
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> On 12/7/15, 5:02 PM, "Meng, Yiming"  wrote:
> >> >>>
> >> >>> >
> >> >>> >Quick questions:
> >> >>> >
> >> >>> >1. Are you guys re-implement part of Trident?
> >> >>> >2. How can the type information kept during the data processing by
> >> >>>Storm?
> >> >>> >
> >> >>> >Regards,
> >> >>> >Yiming Meng
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >On 12/7/15, 4:58 PM, "Chen, Hao"  wrote:
> >> >>> >
> >> >>> >>It¹s very good point and 

[jira] [Updated] (EAGLE-53) Docker Image for Eagle

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-53:
--
Assignee: Zhaokun Qin  (was: Hao Chen)

> Docker Image for Eagle
> --
>
> Key: EAGLE-53
> URL: https://issues.apache.org/jira/browse/EAGLE-53
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
> Environment: docker 1.9.0
>Reporter: Zhaokun Qin
>Assignee: Zhaokun Qin
>  Labels: Integration
> Fix For: 0.3.0
>
>
> {code}
> docker pull apacheeagle/sandbox
> docker run -p 9099:9099 -p 8080:8080 -p 8744:8744 -p 2181:2181 -p 2888:2888 \
>   -p 6667:6667 -p 60020:60020 -p 60030:60030 -p 60010:60010 -d --dns 
> 127.0.0.1 \
>   --entrypoint /usr/local/serf/bin/start-serf-agent.sh -e KEYCHAIN= \
>   --env EAGLE_SERVER_HOST=sandbox.eagle.incubator.apache.org --name sandbox \
>   -h sandbox.eagle.incubator.apache.org --privileged=true 
> apacheeagle/sandbox:latest \
>   --tag ambari-server=true
> docker run -it --rm -e EXPECTED_HOST_COUNT=1 -e 
> BLUEPRINT=hdp-singlenode-eagle \  
>   --link sandbox:ambariserver --entrypoint /bin/sh apacheeagle/sandbox:latest 
> \
>   -c /tmp/install-cluster.sh
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-78:
--
Assignee: Zhaokun Qin  (was: Hao Chen)

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Zhaokun Qin (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057588#comment-15057588
 ] 

Zhaokun Qin commented on EAGLE-78:
--

the below information is from docker ambari's issue to solve the problem in 
window and mac.

The default shell in boot2docker VM is sh, which doesn't support functions as 
well.

docker@boot2docker:~$ ps -p $$
PID TTY  TIME CMD
19277 pts/100:00:00 sh

To use the ambari-functions you have to execute it on Bash. If you are a mac 
user it's quite easy, because the default shell is bash. Just source 
ambari-functions locally. You only need to take care a routing rule, because 
otherwise the ambari-functions couldn't connect to the docker containers inside 
the VM.

sudo route add -net 172.17.0.0/16 192.168.59.103
If you are on Windows, you have to install bash first

tce-load -wi bash
bash

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-78:
--
Comment: was deleted

(was: Good catch, could you please submit a pull request for the fix?)

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Hao Chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057617#comment-15057617
 ] 

Hao Chen commented on EAGLE-78:
---

Good catch, could you please submit a pull request for the fix?

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Hao Chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057616#comment-15057616
 ] 

Hao Chen commented on EAGLE-78:
---

Good catch, could you please submit a pull request for the fix?

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (EAGLE-78) eagle-lib.sh script not work for mac osx and windows

[Hao Chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057616#comment-15057616
 ] 

Hao Chen edited comment on EAGLE-78 at 12/15/15 8:32 AM:
-

Good catch, could you please submit a pull request for the fix to force 
executing with bash?


was (Author: haoch):
Good catch, could you please submit a pull request for the fix?

> eagle-lib.sh script not work for mac osx and windows
> 
>
> Key: EAGLE-78
> URL: https://issues.apache.org/jira/browse/EAGLE-78
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
> Environment: mac osx, windows
>Reporter: Hao Chen
>Assignee: Zhaokun Qin
> Fix For: 0.3.0
>
>
> Error under MacOSX
> {code}
> $ source eagle-external/eagle-docker/bin/eagle-lib.sh
> -sh: `run-command': not a valid identifier
> -sh: `amb-clean': not a valid identifier
> -sh: `get-ambari-server-ip': not a valid identifier
> -sh: `get-host-ip': not a valid identifier
> -sh: `amb-members': not a valid identifier
> -sh: `amb-settings': not a valid identifier
> -sh: `docker-ps': not a valid identifier
> -sh: `docker-psa': not a valid identifier
> -sh: `amb-start-cluster': not a valid identifier
> -sh: `amb-shell': not a valid identifier
> -sh: `eagle-deploy-cluster': not a valid identifier
> -sh: `amb-start-first': not a valid identifier
> -sh: `amb-copy-to-hdfs': not a valid identifier
> -sh: `amb-create-hdfs-dir': not a valid identifier
> -sh: `amb-scp-to-first': not a valid identifier
> -sh: `amb-start-node': not a valid identifier
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-88 : Eagle web-service should ...

[RalphSu]

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/32

EAGLE-88 : Eagle web-service should have status url

https://issues.apache.org/jira/browse/EAGLE-88

Clear the dependency to make dev able to start eagle-service with mvn 
tomcat7:run
Add template monitor resource which returns OK for external monitoring

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/32.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #32


commit c8c8408ec7e02b1eb92b89770cc9838bb14dcf86
Author: Su 
Date:   2015-12-15T07:54:11Z

EAGLE-88: Eagle web-service should have status url

https://issues.apache.org/jira/browse/EAGLE-88

Clear the dependency to make dev able to start eagle-service with mvn 
tomcat7:run
Add template monitor resource which returns OK for external monitoring

commit e520e473542ae2a3eb95a5474ef38ce76f442336
Author: Su 
Date:   2015-12-15T08:22:23Z

version as maven property

commit 6fc745a4e1e27d93049275f170df25a544c5ed45
Author: Su 
Date:   2015-12-15T08:26:12Z

add more scala templates

commit d9edf6c6f882ba9f1a0f3d97a1c04e45daf91444
Author: Su 
Date:   2015-12-15T08:29:04Z

remove author info




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-88) Eagle web-service should have status url

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057621#comment-15057621
 ] 

ASF GitHub Bot commented on EAGLE-88:
-

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/32

EAGLE-88 : Eagle web-service should have status url

https://issues.apache.org/jira/browse/EAGLE-88

Clear the dependency to make dev able to start eagle-service with mvn 
tomcat7:run
Add template monitor resource which returns OK for external monitoring

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/32.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #32


commit c8c8408ec7e02b1eb92b89770cc9838bb14dcf86
Author: Su 
Date:   2015-12-15T07:54:11Z

EAGLE-88: Eagle web-service should have status url

https://issues.apache.org/jira/browse/EAGLE-88

Clear the dependency to make dev able to start eagle-service with mvn 
tomcat7:run
Add template monitor resource which returns OK for external monitoring

commit e520e473542ae2a3eb95a5474ef38ce76f442336
Author: Su 
Date:   2015-12-15T08:22:23Z

version as maven property

commit 6fc745a4e1e27d93049275f170df25a544c5ed45
Author: Su 
Date:   2015-12-15T08:26:12Z

add more scala templates

commit d9edf6c6f882ba9f1a0f3d97a1c04e45daf91444
Author: Su 
Date:   2015-12-15T08:29:04Z

remove author info




> Eagle web-service should have status url
> 
>
> Key: EAGLE-88
> URL: https://issues.apache.org/jira/browse/EAGLE-88
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> As a standalone service, eagle-service should have status url which expose 
> the system status. 
> This is the convention that for a service should make itself reachable and 
> monitor-able, and by have this status url service downgrade would be 
> possible. And this url is good fit of dropwizard metrics expose.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-14) Re-assemble high level hdfs commands for better policy

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057630#comment-15057630
 ] 

ASF GitHub Bot commented on EAGLE-14:
-

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/25#discussion_r47609881
  
--- Diff: test.txt ---
@@ -0,0 +1 @@
+test for keep file for user command reassembler
--- End diff --

Why keep the `test.txt` file in code base?


> Re-assemble high level hdfs commands for better policy
> --
>
> Key: EAGLE-14
> URL: https://issues.apache.org/jira/browse/EAGLE-14
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: 0.3.0
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> User today can use Eagle to create policy against the finest granularity of 
> hdfs command for example getFileInfo, list, delete etc., but that sometimes 
> is not good for defining a policy against a user's native command.
> Hdfs client would interpret user's high level command into multiple fine 
> commands and send those fine commands to Hdfs server which in turn are logged 
> into namenode audit log. For example one copyToLocal high-level command 
> probably involves multiple fine commands like rename, move, delete etc.
> Eagle should have a capability to re-assemble those command in real-time to 
> let user define policy on those high-level commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-14: Hdfs User command re-assem...

[haoch]

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/25#discussion_r47609881
  
--- Diff: test.txt ---
@@ -0,0 +1 @@
+test for keep file for user command reassembler
--- End diff --

Why keep the `test.txt` file in code base?


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: [EAGLE-62] Add jshint for front end ...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/18#issuecomment-164692363
  
Merged. @zombieJ 


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-62) Add jshint for front end UI building

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057659#comment-15057659
 ] 

ASF GitHub Bot commented on EAGLE-62:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/18#issuecomment-164692363
  
Merged. @zombieJ 


> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
>
> Currently use grunt for front-end building. Add jshint for code check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: [EAGLE-62] Add jshint for front end ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/18


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-62) Add jshint for front end UI building

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057664#comment-15057664
 ] 

ASF GitHub Bot commented on EAGLE-62:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/18


> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
>
> Currently use grunt for front-end building. Add jshint for code check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-62) Add jshint for front end UI building

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen resolved EAGLE-62.
---
Resolution: Fixed

> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Hao Chen
>Priority: Minor
>
> Currently use grunt for front-end building. Add jshint for code check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-62) Add jshint for front end UI building

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen updated EAGLE-62:
--
Assignee: Jilin, Jiang  (was: Hao Chen)

> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
>
> Currently use grunt for front-end building. Add jshint for code check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-62) Add jshint for front end UI building

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen closed EAGLE-62.
-

> Add jshint for front end UI building
> 
>
> Key: EAGLE-62
> URL: https://issues.apache.org/jira/browse/EAGLE-62
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
>
> Currently use grunt for front-end building. Add jshint for code check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Confluence Page Edit/Create new Page Access

[Senthil Kumar]

Hi Team , Can someone help/guide me to get  edit access to Eagle Confluence
page  ??

https://cwiki.apache.org/confluence/display/EAG/Design


--Senthil

Re: Confluence Page Edit/Create new Page Access

[Chen, Hao]

What’s you wiki account?




On 12/15/15, 5:55 PM, "Senthil Kumar"  wrote:

>Hi Team , Can someone help/guide me to get  edit access to Eagle Confluence
>page  ??
>
>https://cwiki.apache.org/confluence/display/EAG/Design
>
>
>--Senthil

Re: Confluence Page Edit/Create new Page Access

[Senthil Kumar]

username : senthilec566

--Senthil

On Tue, Dec 15, 2015 at 3:27 PM, Chen, Hao  wrote:

> What’s you wiki account?
>
>
>
>
> On 12/15/15, 5:55 PM, "Senthil Kumar"  wrote:
>
> >Hi Team , Can someone help/guide me to get  edit access to Eagle
> Confluence
> >page  ??
> >
> >https://cwiki.apache.org/confluence/display/EAG/Design
> >
> >
> >--Senthil
>

Re: Confluence Page Edit/Create new Page Access

[Chen, Hao]

Done.



On 12/15/15, 5:58 PM, "Senthil Kumar"  wrote:

>username : senthilec566
>
>--Senthil
>
>On Tue, Dec 15, 2015 at 3:27 PM, Chen, Hao  wrote:
>
>> What’s you wiki account?
>>
>>
>>
>>
>> On 12/15/15, 5:55 PM, "Senthil Kumar"  wrote:
>>
>> >Hi Team , Can someone help/guide me to get  edit access to Eagle
>> Confluence
>> >page  ??
>> >
>> >https://cwiki.apache.org/confluence/display/EAG/Design
>> >
>> >
>> >--Senthil
>>

Re: Confluence Page Edit/Create new Page Access

[Senthil Kumar]

Thanks Hao!

On Tue, Dec 15, 2015 at 3:30 PM, Chen, Hao  wrote:

> Done.
>
>
>
> On 12/15/15, 5:58 PM, "Senthil Kumar"  wrote:
>
> >username : senthilec566
> >
> >--Senthil
> >
> >On Tue, Dec 15, 2015 at 3:27 PM, Chen, Hao  wrote:
> >
> >> What’s you wiki account?
> >>
> >>
> >>
> >>
> >> On 12/15/15, 5:55 PM, "Senthil Kumar"  wrote:
> >>
> >> >Hi Team , Can someone help/guide me to get  edit access to Eagle
> >> Confluence
> >> >page  ??
> >> >
> >> >https://cwiki.apache.org/confluence/display/EAG/Design
> >> >
> >> >
> >> >--Senthil
> >>
>

[jira] [Commented] (EAGLE-76) Disable creating newStream for common user role

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057756#comment-15057756
 ] 

ASF GitHub Bot commented on EAGLE-76:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/31


> Disable creating newStream for common user role
> ---
>
> Key: EAGLE-76
> URL: https://issues.apache.org/jira/browse/EAGLE-76
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Jilin, Jiang
>Priority: Minor
>
> for a regular user, he/she should not have a right to create a new stream. We 
> should hide this function. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: [EAGLE-76] hide stream operation if ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/31


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: [EAGLE-76] hide stream operation if ...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/31#issuecomment-164717211
  
Please resolve the JIRA ticket as well: 
https://issues.apache.org/jira/browse/EAGLE-76


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-76) Disable creating newStream for common user role

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057808#comment-15057808
 ] 

ASF GitHub Bot commented on EAGLE-76:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/31#issuecomment-164717211
  
Please resolve the JIRA ticket as well: 
https://issues.apache.org/jira/browse/EAGLE-76


> Disable creating newStream for common user role
> ---
>
> Key: EAGLE-76
> URL: https://issues.apache.org/jira/browse/EAGLE-76
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Jilin, Jiang
>Priority: Minor
>
> for a regular user, he/she should not have a right to create a new stream. We 
> should hide this function. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-47) Ability to audit who made changes to Eagle policies

[Murali Krishna (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murali Krishna updated EAGLE-47:

Attachment: eagle_47_design.docx

Design document to be reviewed is attached.

> Ability to audit who made changes to Eagle policies
> ---
>
> Key: EAGLE-47
> URL: https://issues.apache.org/jira/browse/EAGLE-47
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Arun Manoharan
>Assignee: Senthilkumar
> Fix For: 0.3.0
>
> Attachments: eagle_47_design.docx
>
>
> As an admin of Apache Eagle I would like to know who created policies, 
> modified policies, Deleted policies.
> Also who added source, site etc.
> This information is a must have for security related products to have an 
> audit trail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

https://issues.apache.org/jira/browse/EAGLE-47

[Senthil Kumar]

Hi All , Pls review the approach for Eagle 47 issue and let us know the
comments/suggestions ..

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332673


Open Question :

  Current Eagle Service consider UPDATE request also CREAT i.e  When user
updates policy in UI the ROW will be replaced in HBASE..

We should add some placeholder to indicate that this Request is UPDATE when
invoking update call..

Pls add your comments...


--Senthil

[jira] [Created] (EAGLE-89) Rest Api refresh takes forever if Hbase is down. Timeout needed.

[hemanth dendukuri (JIRA)]

hemanth dendukuri created EAGLE-89:
--

 Summary: Rest Api refresh takes forever if Hbase is down. Timeout 
needed. 
 Key: EAGLE-89
 URL: https://issues.apache.org/jira/browse/EAGLE-89
 Project: Eagle
  Issue Type: Bug
 Environment: Hortonworks Sandbox
Reporter: hemanth dendukuri


Eagle Web Service Rest Api takes forever to respond if hbase is down.

Every rest api calls should have timeout to respond and provide appropriate 
error in case of failure.

Can reproduce this issue by stopping the Hbase and accessing link. 
http://127.0.0.1:9099/eagle-service/rest/list?query=AlertDataSourceService[]{*}&pageSize=10




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-90) DefaultPolicyPartitioner hash algorithm is not able to provide efficient partitioning, if the policy names start with similar characters.

[hemanth dendukuri (JIRA)]

hemanth dendukuri created EAGLE-90:
--

 Summary: DefaultPolicyPartitioner hash algorithm is not able to 
provide efficient partitioning, if the policy names start with similar 
characters.
 Key: EAGLE-90
 URL: https://issues.apache.org/jira/browse/EAGLE-90
 Project: Eagle
  Issue Type: Bug
 Environment: Hortonworks Sandbox
Reporter: hemanth dendukuri
Priority: Minor


DefaultPolicyPartitioner returns same partition of three consecutive policies 
with policyId readtmpPII, readtmpPII2, readtmpPIIpii,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

"Last Modified" info missing when created policy by calling API

[Daniel Zhou]

Hi all,

In the UI "Policy List", the policies created using UI have "last modified" 
information, but for the policy created by calling  policy API, that 
information is missing.
How to improve it?

Regards,
Da

[jira] [Created] (EAGLE-91) Hive Policy, Command Value Should be in Capital Letter.

[hemanth dendukuri (JIRA)]

hemanth dendukuri created EAGLE-91:
--

 Summary: Hive Policy, Command Value Should be in Capital Letter.
 Key: EAGLE-91
 URL: https://issues.apache.org/jira/browse/EAGLE-91
 Project: Eagle
  Issue Type: Bug
 Environment: Hortonworks Sandbox
Reporter: hemanth dendukuri



The value of command in hive policy had to always be in capital letters. For 
Example “select” would not work but “SELECE” works.
Policy : from hiveAccessLogStream[(command == ’select')] select * insert into 
outputStream;
Hive command : select distinct phone_number from customer_details;
Actual : Alert not triggered.
Expected: Alert should be triggered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-92) Ambari Eagle Install scripts needs update.

[hemanth dendukuri (JIRA)]

hemanth dendukuri created EAGLE-92:
--

 Summary: Ambari Eagle Install scripts needs update. 
 Key: EAGLE-92
 URL: https://issues.apache.org/jira/browse/EAGLE-92
 Project: Eagle
  Issue Type: Improvement
 Environment: Hortonworks Sandbox
Reporter: hemanth dendukuri
Assignee: Hao Chen


Not able to start Eagle HDFS and other storm services.

ProcessorMain -D 
config.file=/usr/hdp/current/eagle/conf/sandbox-hdfsAuditLog-application.conf 
-D envContextConfig.topologyName=sandbox-hdfsAuditLog-topology
Error: Could not find or load main class 
eagle.security.auditlog.HdfsAuditLogProcessorMain
Failure 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-93) Ambari Eagle Script for uninstall does not remove Eagle Ambari service from Add Service Wizard.

[hemanth dendukuri (JIRA)]

hemanth dendukuri created EAGLE-93:
--

 Summary: Ambari Eagle Script for uninstall does not remove Eagle 
Ambari service from Add Service Wizard.  
 Key: EAGLE-93
 URL: https://issues.apache.org/jira/browse/EAGLE-93
 Project: Eagle
  Issue Type: Bug
 Environment: Hortonworks Sandbox
Reporter: hemanth dendukuri
Assignee: Hao Chen


after running "/usr/hdp/current/eagle/bin/eagle-ambari.sh uninstall", I can 
still go to "Add Service Wizard" from Ambari and add Eagle service. 

We will make Ambari not to work,  If user by mistake try's eagle on latest 
version of Hortonworks sandbox.

have u got this error
Ambari Server and Web Client versions do not match:

Ambari Server: 2.1.0
Ambari Web Client: 2.0.0




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-94) fix the bug of eagle docker in Mac

[Zhaokun Qin (JIRA)]

Zhaokun Qin created EAGLE-94:


 Summary: fix the bug of eagle docker in Mac
 Key: EAGLE-94
 URL: https://issues.apache.org/jira/browse/EAGLE-94
 Project: Eagle
  Issue Type: Bug
Reporter: Zhaokun Qin
 Fix For: 0.3.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Created] (EAGLE-94) fix the bug of eagle docker in Mac

[Zhang, Edward (GDI Hadoop)]

I don¹t see any description of this JIRA, could we put more details into
JIRA for community to leverage this information.

On 12/15/15, 15:52, "Zhaokun Qin (JIRA)"  wrote:

>Zhaokun Qin created EAGLE-94:
>
>
> Summary: fix the bug of eagle docker in Mac
> Key: EAGLE-94
> URL: https://issues.apache.org/jira/browse/EAGLE-94
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhaokun Qin
> Fix For: 0.3.0
>
>
>
>
>
>
>--
>This message was sent by Atlassian JIRA
>(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-94 Add shebang in eagle-lib.sh

[qinzhaokun]

GitHub user qinzhaokun opened a pull request:

https://github.com/apache/incubator-eagle/pull/33

EAGLE-94 Add shebang in eagle-lib.sh

https://issues.apache.org/jira/browse/EAGLE-94

Add Shebang in eagle-lib.sh to fix the bug that eagle-lib.sh cannot be 
sourced in Mac.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qinzhaokun/incubator-eagle EAGLE-94

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/33.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #33


commit 3f08eedf9a86dc7d9b737f4154533774564338e4
Author: qinzhaokun 
Date:   2015-12-16T00:17:36Z

EAGLE-94 Add shebang eagle-lib.sh




---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-94) fix the bug of eagle docker in Mac

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059186#comment-15059186
 ] 

ASF GitHub Bot commented on EAGLE-94:
-

GitHub user qinzhaokun opened a pull request:

https://github.com/apache/incubator-eagle/pull/33

EAGLE-94 Add shebang in eagle-lib.sh

https://issues.apache.org/jira/browse/EAGLE-94

Add Shebang in eagle-lib.sh to fix the bug that eagle-lib.sh cannot be 
sourced in Mac.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qinzhaokun/incubator-eagle EAGLE-94

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/33.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #33


commit 3f08eedf9a86dc7d9b737f4154533774564338e4
Author: qinzhaokun 
Date:   2015-12-16T00:17:36Z

EAGLE-94 Add shebang eagle-lib.sh




> fix the bug of eagle docker in Mac
> --
>
> Key: EAGLE-94
> URL: https://issues.apache.org/jira/browse/EAGLE-94
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhaokun Qin
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-76) Disable creating newStream for common user role

[Jilin, Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jilin, Jiang resolved EAGLE-76.
---
Resolution: Fixed

> Disable creating newStream for common user role
> ---
>
> Key: EAGLE-76
> URL: https://issues.apache.org/jira/browse/EAGLE-76
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Jilin, Jiang
>Priority: Minor
>
> for a regular user, he/she should not have a right to create a new stream. We 
> should hide this function. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-86: Rewrite HDFSAuditLogParser...

[sunlibin]

Github user sunlibin commented on the pull request:

https://github.com/apache/incubator-eagle/pull/29#issuecomment-164964814
  
Thanks for reminder, added the missing hyphen


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-86) Rewrite HDFSAuditLogParser to a non-regular expression version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059367#comment-15059367
 ] 

ASF GitHub Bot commented on EAGLE-86:
-

Github user sunlibin commented on the pull request:

https://github.com/apache/incubator-eagle/pull/29#issuecomment-164964814
  
Thanks for reminder, added the missing hyphen


> Rewrite HDFSAuditLogParser to a non-regular expression version
> --
>
> Key: EAGLE-86
> URL: https://issues.apache.org/jira/browse/EAGLE-86
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Libin, Sun
>Priority: Minor
> Fix For: 0.3.0
>
>
> HDFSAuditLogParser use many regular expressions to parse audit log, which is 
> a bit heavy, to improve topology's throughput, consider to rewrite it to a 
> non-regular expression version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[Code-Review-Request] EAGLE-88 : Eagle web-service should have status url

[Liangfei.Su]

Please help review the request for EAGLE-88 at

https://github.com/apache/incubator-eagle/pull/32

Ralph

[GitHub] incubator-eagle pull request: EAGLE-94 Add shebang in eagle-lib.sh

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/33#issuecomment-164969515
  
LGTM. Will Merge.


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-94) fix the bug of eagle docker in Mac

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059395#comment-15059395
 ] 

ASF GitHub Bot commented on EAGLE-94:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/33#issuecomment-164969515
  
LGTM. Will Merge.


> fix the bug of eagle docker in Mac
> --
>
> Key: EAGLE-94
> URL: https://issues.apache.org/jira/browse/EAGLE-94
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhaokun Qin
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Cluster health monitoring

[Modi, Avinash]

Hi
I wanted to know whether Eagle provides cluster health monitoring, node health 
monitoring and metrics collection like CPU, Physical Memory Used.

Thanks

access request to edit the wiki page

[Krishna, Murali(AWF)]

Hi Team,

Can someone provide me access to edit the Wiki @ 
https://cwiki.apache.org/confluence/display/EAG/Design
userId - murkrishna

Thanks,
Murali Krishna

Re: Cluster health monitoring

[Zhang, Edward (GDI Hadoop)]

hadoop native metric monitoring, mapreduce job monitoring, gc activity
monitoring etc is going to be open sourced in next 2 months. Eagle dev
team is converting/developing code to adapt to current Eagle framework.
Roadmap and some discussion are in
https://cwiki.apache.org/confluence/display/EAG/Apache+Eagle+Roadmap and
https://cwiki.apache.org/confluence/display/EAG/Hadoop+Native+Metrics+Monit
oring

Thanks
Edward

On 12/15/15, 21:03, "Modi, Avinash"  wrote:

>Hi
>I wanted to know whether Eagle provides cluster health monitoring, node
>health monitoring and metrics collection like CPU, Physical Memory Used.
>
>Thanks

[GitHub] incubator-eagle pull request: EAGLE-66 Typesafe Streaming DSL and ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/26


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-66) Eagle TypeSafe Stream Processing DSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059551#comment-15059551
 ] 

ASF GitHub Bot commented on EAGLE-66:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/26


> Eagle TypeSafe Stream Processing DSL
> 
>
> Key: EAGLE-66
> URL: https://issues.apache.org/jira/browse/EAGLE-66
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> h1. Main Features
> 1. Typesafe API: Currently the stream processing API is not type-safe (Type 
> info are erased by stream framework), all programming interfaces for 
> developer are faced to Object/AnyRef, which is not very friendly and 
> extensible for framework user (application developer):
> {code}
> public void flatMap(java.util.List input, Collector AlertAPIEntity>> outputCollector)
> {code}
> So i propose the interface as (all type information are transparent for 
> developer, not need additional parameters, supported by Scala implicit 
> TypeTag)
> {code}class StreamProducer[+T <: Any] extends StreamInfo with 
> StreamProtocol[T]{code}
> * StreamInfo:  contains Stream core information including streamId, 
> processing element id/name, entity type info (class/TypeTag)
> * StreamProtocol extends JavaStreamProtocol: contains basic Stream DSL API 
> and java-compatible API
> {code}
> class StreamInfo  extends Serializable{
>   val id:Int = UniqueId.incrementAndGetId()
>   var name: String = null
>   var streamId:String=null
>   var parallelismNum: Int = 1
>   var inKeyed:Boolean = false
>   var outKeyed:Boolean = false
>   var keySelector:KeySelector = null
>   var typeClass:Class[_] = classOf[AnyRef]
>   @transient  implicit var typeTag:ru.TypeTag[_] = ru.typeTag[AnyRef]
> }
> {code}
> And the StreamInfo can be shared through the runtime as implicit context for 
> execution layer as well:
> {code}
> abstract class AbstractStreamBolt[T](val fieldsNum:Int=0, val ack:Boolean = 
> true)(implicit streamInfo:StreamInfo) extends BaseRichBolt
> {code}
> 2. KeyValue Based Structure: currently framework user (developer) have to 
> handle with field declaration again and again, and framework and business 
> logic are highly coupled, according to the StreamProtocol description, user 
> should not care about framework level detail like internal data structure for 
> Storm using List with Fields which is not friendly for 
> developer, we should make sure user focus on business logic only like:
> {code}
> env.from(tuples)
>   .groupByKey(_.name)
> {code}
> 3. Spout grouping instead of overriding Schema: currently especially in use 
> case like HdfsAuditLog Monitoring, if developer wants to  groupby certain 
> key, they are forced to override Schema (specific for storm) , which is not 
> good and un-reusable.
> 4. Environment Decoupled: currently the stream (metadata) /dag (logic) / 
> environment (execution) are coupled with storm internal implementation, which 
> is not good for becoming a metadata-driven pipeline framework in future, so 
> we should decouple it.
>  
> 5. Compatible with Field-based Structure in old framework and application.
> 6. Configuration: enhanced config wrapper upon typesafe-config for supporting 
> get/set/default and integrated with ExecutionEnvironment
> {code}
> val env = ExecutionEnvironments.get[StormExecutionEnvironment](args)
>   val streamName = env.config.get[String]("eagle.stream.name","eventStream")
>   val streamExecutorId = 
> env.config.get[String]("eagle.stream.executor",s"${streamName}Executor")
>   
> env.config.set("dataSourceConfig.deserializerClass",classOf[JsonMessageDeserializer].getCanonicalName)
> {code}
> h1. Sample Application
> {code}
> case class Entity(name:String,value:Double,var inc:Int=0)
> val tuples = Seq(
>   Entity("a", 1),
>   Entity("a", 2),
>   Entity("a", 3),
>   Entity("b", 2),
>   Entity("c", 3),
>   Entity("d", 3)
> )
> val env = ExecutionEnvironments.get[StormExecutionEnvironment](args)
> // DAG is fully automatically aware: Entity -> Tuple2 -> Tuple3 
> env.from(tuples)
>   .groupByKey(_.name)
>   .map(o => {o.inc += 2;o})
>   .filter(_.name != "b")
>   .filter(_.name != "c")
>   .groupByKey(o=>(o.name,o.value))
>   .map(o => (o.name,o))
>   .map(o => (o._1,o._2.value,o._2.inc))
>   .foreach(println)
>  env.execute()
> {code}
> Type is transparent for developer during both DAG compiling (programming) and 
> runtime (metadata) phases
> {code}
> 2015-12-07 15:17:19,820 INFO [main] utils.GraphPrinter$[43]: Before expanded 
> DAG 
> { 
>   IterableStreamProducer[Entity]_1{1} -> 
> GroupByKeyProducer[(Entity)]_2{1} in shuffleGroup
>   GroupByKeyProducer[(Entity)]_2{1

[GitHub] incubator-eagle pull request: EAGLE-66 Typesafe Streaming DSL and ...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/26#issuecomment-165007280
  
Merged


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-66) Eagle TypeSafe Stream Processing DSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059552#comment-15059552
 ] 

ASF GitHub Bot commented on EAGLE-66:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/26#issuecomment-165007280
  
Merged


> Eagle TypeSafe Stream Processing DSL
> 
>
> Key: EAGLE-66
> URL: https://issues.apache.org/jira/browse/EAGLE-66
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> h1. Main Features
> 1. Typesafe API: Currently the stream processing API is not type-safe (Type 
> info are erased by stream framework), all programming interfaces for 
> developer are faced to Object/AnyRef, which is not very friendly and 
> extensible for framework user (application developer):
> {code}
> public void flatMap(java.util.List input, Collector AlertAPIEntity>> outputCollector)
> {code}
> So i propose the interface as (all type information are transparent for 
> developer, not need additional parameters, supported by Scala implicit 
> TypeTag)
> {code}class StreamProducer[+T <: Any] extends StreamInfo with 
> StreamProtocol[T]{code}
> * StreamInfo:  contains Stream core information including streamId, 
> processing element id/name, entity type info (class/TypeTag)
> * StreamProtocol extends JavaStreamProtocol: contains basic Stream DSL API 
> and java-compatible API
> {code}
> class StreamInfo  extends Serializable{
>   val id:Int = UniqueId.incrementAndGetId()
>   var name: String = null
>   var streamId:String=null
>   var parallelismNum: Int = 1
>   var inKeyed:Boolean = false
>   var outKeyed:Boolean = false
>   var keySelector:KeySelector = null
>   var typeClass:Class[_] = classOf[AnyRef]
>   @transient  implicit var typeTag:ru.TypeTag[_] = ru.typeTag[AnyRef]
> }
> {code}
> And the StreamInfo can be shared through the runtime as implicit context for 
> execution layer as well:
> {code}
> abstract class AbstractStreamBolt[T](val fieldsNum:Int=0, val ack:Boolean = 
> true)(implicit streamInfo:StreamInfo) extends BaseRichBolt
> {code}
> 2. KeyValue Based Structure: currently framework user (developer) have to 
> handle with field declaration again and again, and framework and business 
> logic are highly coupled, according to the StreamProtocol description, user 
> should not care about framework level detail like internal data structure for 
> Storm using List with Fields which is not friendly for 
> developer, we should make sure user focus on business logic only like:
> {code}
> env.from(tuples)
>   .groupByKey(_.name)
> {code}
> 3. Spout grouping instead of overriding Schema: currently especially in use 
> case like HdfsAuditLog Monitoring, if developer wants to  groupby certain 
> key, they are forced to override Schema (specific for storm) , which is not 
> good and un-reusable.
> 4. Environment Decoupled: currently the stream (metadata) /dag (logic) / 
> environment (execution) are coupled with storm internal implementation, which 
> is not good for becoming a metadata-driven pipeline framework in future, so 
> we should decouple it.
>  
> 5. Compatible with Field-based Structure in old framework and application.
> 6. Configuration: enhanced config wrapper upon typesafe-config for supporting 
> get/set/default and integrated with ExecutionEnvironment
> {code}
> val env = ExecutionEnvironments.get[StormExecutionEnvironment](args)
>   val streamName = env.config.get[String]("eagle.stream.name","eventStream")
>   val streamExecutorId = 
> env.config.get[String]("eagle.stream.executor",s"${streamName}Executor")
>   
> env.config.set("dataSourceConfig.deserializerClass",classOf[JsonMessageDeserializer].getCanonicalName)
> {code}
> h1. Sample Application
> {code}
> case class Entity(name:String,value:Double,var inc:Int=0)
> val tuples = Seq(
>   Entity("a", 1),
>   Entity("a", 2),
>   Entity("a", 3),
>   Entity("b", 2),
>   Entity("c", 3),
>   Entity("d", 3)
> )
> val env = ExecutionEnvironments.get[StormExecutionEnvironment](args)
> // DAG is fully automatically aware: Entity -> Tuple2 -> Tuple3 
> env.from(tuples)
>   .groupByKey(_.name)
>   .map(o => {o.inc += 2;o})
>   .filter(_.name != "b")
>   .filter(_.name != "c")
>   .groupByKey(o=>(o.name,o.value))
>   .map(o => (o.name,o))
>   .map(o => (o._1,o._2.value,o._2.inc))
>   .foreach(println)
>  env.execute()
> {code}
> Type is transparent for developer during both DAG compiling (programming) and 
> runtime (metadata) phases
> {code}
> 2015-12-07 15:17:19,820 INFO [main] utils.GraphPrinter$[43]: Before expanded 
> DAG 
> { 
>   IterableStreamProducer[Entity]_1{1} -> 
> GroupByKeyProducer[(Entity)]_2{1} in shuffleGroup
>

[GitHub] incubator-eagle pull request: EAGLE 75: Integrate dropwizard metri...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-165010413
  
Please fix the title referring to 
https://cwiki.apache.org/confluence/display/EAG/Contributing+to+Eagle 


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-94 Add shebang in eagle-lib.sh

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/33


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (EAGLE-94) fix the bug of eagle docker in Mac

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen resolved EAGLE-94.
---
Resolution: Fixed

> fix the bug of eagle docker in Mac
> --
>
> Key: EAGLE-94
> URL: https://issues.apache.org/jira/browse/EAGLE-94
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-66 Typesafe Streaming DSL and ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/17


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-66) Eagle TypeSafe Stream Processing DSL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059561#comment-15059561
 ] 

ASF GitHub Bot commented on EAGLE-66:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/17


> Eagle TypeSafe Stream Processing DSL
> 
>
> Key: EAGLE-66
> URL: https://issues.apache.org/jira/browse/EAGLE-66
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>
> h1. Main Features
> 1. Typesafe API: Currently the stream processing API is not type-safe (Type 
> info are erased by stream framework), all programming interfaces for 
> developer are faced to Object/AnyRef, which is not very friendly and 
> extensible for framework user (application developer):
> {code}
> public void flatMap(java.util.List input, Collector AlertAPIEntity>> outputCollector)
> {code}
> So i propose the interface as (all type information are transparent for 
> developer, not need additional parameters, supported by Scala implicit 
> TypeTag)
> {code}class StreamProducer[+T <: Any] extends StreamInfo with 
> StreamProtocol[T]{code}
> * StreamInfo:  contains Stream core information including streamId, 
> processing element id/name, entity type info (class/TypeTag)
> * StreamProtocol extends JavaStreamProtocol: contains basic Stream DSL API 
> and java-compatible API
> {code}
> class StreamInfo  extends Serializable{
>   val id:Int = UniqueId.incrementAndGetId()
>   var name: String = null
>   var streamId:String=null
>   var parallelismNum: Int = 1
>   var inKeyed:Boolean = false
>   var outKeyed:Boolean = false
>   var keySelector:KeySelector = null
>   var typeClass:Class[_] = classOf[AnyRef]
>   @transient  implicit var typeTag:ru.TypeTag[_] = ru.typeTag[AnyRef]
> }
> {code}
> And the StreamInfo can be shared through the runtime as implicit context for 
> execution layer as well:
> {code}
> abstract class AbstractStreamBolt[T](val fieldsNum:Int=0, val ack:Boolean = 
> true)(implicit streamInfo:StreamInfo) extends BaseRichBolt
> {code}
> 2. KeyValue Based Structure: currently framework user (developer) have to 
> handle with field declaration again and again, and framework and business 
> logic are highly coupled, according to the StreamProtocol description, user 
> should not care about framework level detail like internal data structure for 
> Storm using List with Fields which is not friendly for 
> developer, we should make sure user focus on business logic only like:
> {code}
> env.from(tuples)
>   .groupByKey(_.name)
> {code}
> 3. Spout grouping instead of overriding Schema: currently especially in use 
> case like HdfsAuditLog Monitoring, if developer wants to  groupby certain 
> key, they are forced to override Schema (specific for storm) , which is not 
> good and un-reusable.
> 4. Environment Decoupled: currently the stream (metadata) /dag (logic) / 
> environment (execution) are coupled with storm internal implementation, which 
> is not good for becoming a metadata-driven pipeline framework in future, so 
> we should decouple it.
>  
> 5. Compatible with Field-based Structure in old framework and application.
> 6. Configuration: enhanced config wrapper upon typesafe-config for supporting 
> get/set/default and integrated with ExecutionEnvironment
> {code}
> val env = ExecutionEnvironments.get[StormExecutionEnvironment](args)
>   val streamName = env.config.get[String]("eagle.stream.name","eventStream")
>   val streamExecutorId = 
> env.config.get[String]("eagle.stream.executor",s"${streamName}Executor")
>   
> env.config.set("dataSourceConfig.deserializerClass",classOf[JsonMessageDeserializer].getCanonicalName)
> {code}
> h1. Sample Application
> {code}
> case class Entity(name:String,value:Double,var inc:Int=0)
> val tuples = Seq(
>   Entity("a", 1),
>   Entity("a", 2),
>   Entity("a", 3),
>   Entity("b", 2),
>   Entity("c", 3),
>   Entity("d", 3)
> )
> val env = ExecutionEnvironments.get[StormExecutionEnvironment](args)
> // DAG is fully automatically aware: Entity -> Tuple2 -> Tuple3 
> env.from(tuples)
>   .groupByKey(_.name)
>   .map(o => {o.inc += 2;o})
>   .filter(_.name != "b")
>   .filter(_.name != "c")
>   .groupByKey(o=>(o.name,o.value))
>   .map(o => (o.name,o))
>   .map(o => (o._1,o._2.value,o._2.inc))
>   .foreach(println)
>  env.execute()
> {code}
> Type is transparent for developer during both DAG compiling (programming) and 
> runtime (metadata) phases
> {code}
> 2015-12-07 15:17:19,820 INFO [main] utils.GraphPrinter$[43]: Before expanded 
> DAG 
> { 
>   IterableStreamProducer[Entity]_1{1} -> 
> GroupByKeyProducer[(Entity)]_2{1} in shuffleGroup
>   GroupByKeyProducer[(Entity)]_2{1

[jira] [Closed] (EAGLE-94) fix the bug of eagle docker in Mac

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen closed EAGLE-94.
-

> fix the bug of eagle docker in Mac
> --
>
> Key: EAGLE-94
> URL: https://issues.apache.org/jira/browse/EAGLE-94
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhaokun Qin
>Assignee: Hao Chen
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-94) fix the bug of eagle docker in Mac

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059560#comment-15059560
 ] 

ASF GitHub Bot commented on EAGLE-94:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/33


> fix the bug of eagle docker in Mac
> --
>
> Key: EAGLE-94
> URL: https://issues.apache.org/jira/browse/EAGLE-94
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhaokun Qin
> Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: access request to edit the wiki page

[Hao Chen]

Murali,

Added you into wiki. And did you sign ICLA?

Regards,
Hao


On Wed, Dec 16, 2015 at 1:36 PM, Krishna, Murali(AWF) 
wrote:

> Hi Team,
>
> Can someone provide me access to edit the Wiki @
> https://cwiki.apache.org/confluence/display/EAG/Design
> userId - murkrishna
>
> Thanks,
> Murali Krishna
>

[GitHub] incubator-eagle pull request: EAGLE-75: Integrate dropwizard metri...

[sunlibin]

Github user sunlibin commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-165023373
  
Added the missing hyphen of the title


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-75) Leverage dropwizard metrics for generating Eagle Topology and DataSource Metrics

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059644#comment-15059644
 ] 

ASF GitHub Bot commented on EAGLE-75:
-

Github user sunlibin commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-165023373
  
Added the missing hyphen of the title


> Leverage dropwizard metrics for generating Eagle Topology and DataSource 
> Metrics
> 
>
> Key: EAGLE-75
> URL: https://issues.apache.org/jira/browse/EAGLE-75
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Libin, Sun
> Fix For: 0.3.0
>
>
> As a monitoring system, eagle need to report & record both the datasource 
> data distribution metric & topology running status metrics to let user have 
> better understanding of the system running status.
> Previously we added a simple metric framework to support user cases like 
> [EAGLE-2](https://issues.apache.org/jira/browse/EAGLE-2) , 
> [EAGLE-24](https://issues.apache.org/jira/browse/EAGLE-24)
> Considering we will have a lot metric user cases to onboard later, we need a 
> better metric framework to make it easier to support these cases, and after 
> some investigation, we found [Dropwizard 
> metrics](https://github.com/dropwizard/metrics) is a good one that can match 
> our needs, So we want to integrate Dropwizard metrics with eagle 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-75: Integrate dropwizard metri...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-165023954
  
LGTM, please merge according to 
https://cwiki.apache.org/confluence/display/EAG/Contributing+to+Eagle


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-75) Leverage dropwizard metrics for generating Eagle Topology and DataSource Metrics

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059650#comment-15059650
 ] 

ASF GitHub Bot commented on EAGLE-75:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/28#issuecomment-165023954
  
LGTM, please merge according to 
https://cwiki.apache.org/confluence/display/EAG/Contributing+to+Eagle


> Leverage dropwizard metrics for generating Eagle Topology and DataSource 
> Metrics
> 
>
> Key: EAGLE-75
> URL: https://issues.apache.org/jira/browse/EAGLE-75
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Libin, Sun
> Fix For: 0.3.0
>
>
> As a monitoring system, eagle need to report & record both the datasource 
> data distribution metric & topology running status metrics to let user have 
> better understanding of the system running status.
> Previously we added a simple metric framework to support user cases like 
> [EAGLE-2](https://issues.apache.org/jira/browse/EAGLE-2) , 
> [EAGLE-24](https://issues.apache.org/jira/browse/EAGLE-24)
> Considering we will have a lot metric user cases to onboard later, we need a 
> better metric framework to make it easier to support these cases, and after 
> some investigation, we found [Dropwizard 
> metrics](https://github.com/dropwizard/metrics) is a good one that can match 
> our needs, So we want to integrate Dropwizard metrics with eagle 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-86: Rewrite HDFSAuditLogParser...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/29#issuecomment-165024009
  
LGTM, please merge accordingly.


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-86) Rewrite HDFSAuditLogParser to a non-regular expression version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059652#comment-15059652
 ] 

ASF GitHub Bot commented on EAGLE-86:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/29#issuecomment-165024009
  
LGTM, please merge accordingly.


> Rewrite HDFSAuditLogParser to a non-regular expression version
> --
>
> Key: EAGLE-86
> URL: https://issues.apache.org/jira/browse/EAGLE-86
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Libin, Sun
>Assignee: Libin, Sun
>Priority: Minor
> Fix For: 0.3.0
>
>
> HDFSAuditLogParser use many regular expressions to parse audit log, which is 
> a bit heavy, to improve topology's throughput, consider to rewrite it to a 
> non-regular expression version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-88 : Eagle web-service should ...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/32#issuecomment-165024160
  
LGTM, will merge.


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-88) Eagle web-service should have status url

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059655#comment-15059655
 ] 

ASF GitHub Bot commented on EAGLE-88:
-

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/32#issuecomment-165024160
  
LGTM, will merge.


> Eagle web-service should have status url
> 
>
> Key: EAGLE-88
> URL: https://issues.apache.org/jira/browse/EAGLE-88
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> As a standalone service, eagle-service should have status url which expose 
> the system status. 
> This is the convention that for a service should make itself reachable and 
> monitor-able, and by have this status url service downgrade would be 
> possible. And this url is good fit of dropwizard metrics expose.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-88) Eagle web-service should have status url

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059661#comment-15059661
 ] 

ASF GitHub Bot commented on EAGLE-88:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/32


> Eagle web-service should have status url
> 
>
> Key: EAGLE-88
> URL: https://issues.apache.org/jira/browse/EAGLE-88
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: 0.3.0
>
>
> As a standalone service, eagle-service should have status url which expose 
> the system status. 
> This is the convention that for a service should make itself reachable and 
> monitor-able, and by have this status url service downgrade would be 
> possible. And this url is good fit of dropwizard metrics expose.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-88 : Eagle web-service should ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/32


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---