[jira] [Commented] (EAGLE-426) Load app web classes and app topology classes using configured lib dir

[ https://issues.apache.org/jira/browse/EAGLE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412095#comment-15412095 ] ASF GitHub Bot commented on EAGLE-426: -- Github user yonzhang closed the pull request at:

[GitHub] incubator-eagle pull request #310: Load app web classes and app topology cla...

Github user yonzhang closed the pull request at: https://github.com/apache/incubator-eagle/pull/310 --- 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

Re: [HELP] cannot upload eagle jars to maven repository

So, we need to file 2 infra tickets: 1. One is to add target in Maven repository for Eagle. You can see sample from here: https://issues.apache.org/jira/browse/INFRA-8026 or https://issues.apache.org/jira/browse/INFRA-7246 2. Create ticket for you to be granted karma to access Apache Nexus repo.

[jira] [Comment Edited] (EAGLE-430) explore new packaging method for eagle using new app framework

[ https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412931#comment-15412931 ] Hao Chen edited comment on EAGLE-430 at 8/9/16 4:52 AM: The entry point for

[jira] [Created] (EAGLE-428) Hbase monitoring's metadata browse API in new app framework

Edward Zhang created EAGLE-428: -- Summary: Hbase monitoring's metadata browse API in new app framework Key: EAGLE-428 URL: https://issues.apache.org/jira/browse/EAGLE-428 Project: Eagle Issue

[jira] [Created] (EAGLE-429) CoordinatorTest.test_01 sometimes fail

Edward Zhang created EAGLE-429: -- Summary: CoordinatorTest.test_01 sometimes fail Key: EAGLE-429 URL: https://issues.apache.org/jira/browse/EAGLE-429 Project: Eagle Issue Type: Bug Affects

[jira] [Commented] (EAGLE-428) Hbase monitoring's metadata browse API in new app framework

[ https://issues.apache.org/jira/browse/EAGLE-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412762#comment-15412762 ] ASF GitHub Bot commented on EAGLE-428: -- GitHub user yonzhang opened a pull request:

[GitHub] incubator-eagle issue #309: [EAGLE-422] eagle support for mr & spark running...

Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/309 testApplicationDescWrapperConfigLoadFromXML failed in Jenkins. While unit tests all passed in local --- If your project is set up for it, you can reply to this email and have your

[GitHub] incubator-eagle pull request #309: [EAGLE-422] eagle support for mr & spark ...

Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/309 --- 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

[jira] [Commented] (EAGLE-429) CoordinatorTest.test_01 sometimes fail

[ https://issues.apache.org/jira/browse/EAGLE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412737#comment-15412737 ] Edward Zhang commented on EAGLE-429: Maybe that is because of some temporary failure of zk 2016-08-08

[jira] [Commented] (EAGLE-430) explore new packaging method for eagle using new app framework

[ https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412922#comment-15412922 ] Hao Chen commented on EAGLE-430: The package structure should be as following, and we shouldn't separate

[jira] [Commented] (EAGLE-431) MetadataDaoFactory should use config from eagle server

[ https://issues.apache.org/jira/browse/EAGLE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412941#comment-15412941 ] Hao Chen commented on EAGLE-431: We should handle all Dao in standard registry method in Guice Module. >

Re: [Discuss] How do you think rename "develop" branch to "trunk"branch so that able to close pull request automatically?

Thanks very much for all the feedback. *As a conclusion, based on the above discussions, eagle community agree consistently to rename "develop" branch to "master" branch as the main development branch. The action will happen in one or two days.* - Hao On Tue, Aug 9, 2016 at 11:43 AM,

Re: [Discuss] How do you think rename "develop" branch to "trunk"branch so that able to close pull request automatically?

+1 for master, trunk looks more legacy svn naming.. :) On Mon, Aug 8, 2016 at 2:29 PM, Edward Zhang wrote: > Today master branch is only used for mirroring latest stable release branch > because in the first impression, people will use master to build and run. > > To

[jira] [Commented] (EAGLE-430) explore new packaging method for eagle using new app framework

[ https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412931#comment-15412931 ] Hao Chen commented on EAGLE-430: The entry point for front-end module loading is

[jira] [Created] (EAGLE-430) explore new packaging method for eagle using new app framework

Edward Zhang created EAGLE-430: -- Summary: explore new packaging method for eagle using new app framework Key: EAGLE-430 URL: https://issues.apache.org/jira/browse/EAGLE-430 Project: Eagle

[jira] [Commented] (EAGLE-432) Application status monitoring

[ https://issues.apache.org/jira/browse/EAGLE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412938#comment-15412938 ] Hao Chen commented on EAGLE-432: We could refer to

[jira] [Created] (EAGLE-432) Application status monitoring

Edward Zhang created EAGLE-432: -- Summary: Application status monitoring Key: EAGLE-432 URL: https://issues.apache.org/jira/browse/EAGLE-432 Project: Eagle Issue Type: Improvement Affects

[jira] [Commented] (EAGLE-422) eagle support for mr & spark running job monitoring

[ https://issues.apache.org/jira/browse/EAGLE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412964#comment-15412964 ] ASF GitHub Bot commented on EAGLE-422: -- Github user wujinhu closed the pull request at:

[jira] [Created] (EAGLE-431) MetadataDaoFactory should use config from eagle server

Edward Zhang created EAGLE-431: -- Summary: MetadataDaoFactory should use config from eagle server Key: EAGLE-431 URL: https://issues.apache.org/jira/browse/EAGLE-431 Project: Eagle Issue Type:

Re: [Discuss] How do you think rename "develop" branch to "trunk"branch so that able to close pull request automatically?

Today master branch is only used for mirroring latest stable release branch because in the first impression, people will use master to build and run. To avoid too many breaks in master branch, Eagle community starts to use develop branch for bleeding development work. But that is redundant for

Re: [Discuss] Check Style Specification

It is nice. So do we have offline document for us to review Google java style? It is supposed that a lot of warnings will be generated with those code standards. Thanks Edward On 8/7/16, 22:36, "r7raul1...@163.com" wrote: >I fire a jira for checkstyle base on Google Java

Re: [HELP] cannot upload eagle jars to maven repository

Hi Henry, No, eagle never pushed artifacts to ASF Nexus repository. How can we get the access, please? Michael On Mon, Aug 8, 2016 at 2:21 PM, Henry Saputra wrote: > I found Eagle in ASF release dist folder but do not see it in the Nexus > Maven repo

[GitHub] incubator-eagle issue #309: [EAGLE-422] eagle support for mr & spark running...

Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/309 I have removed the sensitive information and update the code --- 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

[jira] [Commented] (EAGLE-422) eagle support for mr & spark running job monitoring

[ https://issues.apache.org/jira/browse/EAGLE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411497#comment-15411497 ] ASF GitHub Bot commented on EAGLE-422: -- Github user wujinhu commented on the issue:

[GitHub] incubator-eagle pull request #311: Sparkstream draft

GitHub user chitin opened a pull request: https://github.com/apache/incubator-eagle/pull/311 Sparkstream draft configuration parameterize, configure spark driver memory You can merge this pull request into a Git repository by running: $ git pull

Re: [Discuss] How do you think rename "develop" branch to "trunk"branch so that able to close pull request automatically?

+1 to move it to master. On Sun, Aug 7, 2016 at 8:09 PM, Julian Hyde wrote: > +1 moving to “trunk” or “master”. > > Regarding the name. These days more projects use the name “master” rather > than “trunk”. (At least, that’s my impression. Hive, for instance, used > “trunk”

[GitHub] incubator-eagle pull request #311: Sparkstream draft

Github user chitin closed the pull request at: https://github.com/apache/incubator-eagle/pull/311 --- 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

Re: [HELP] cannot upload eagle jars to maven repository

I found Eagle in ASF release dist folder but do not see it in the Nexus Maven repo (https://repository.apache.org) Has Eagle pushed artifacts to ASF Nexus repository for prev releases? - Henry On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu wrote: > Hi mentors, > > I was trying

[jira] [Commented] (EAGLE-422) eagle support for mr & spark running job monitoring

[ https://issues.apache.org/jira/browse/EAGLE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411458#comment-15411458 ] ASF GitHub Bot commented on EAGLE-422: -- Github user qingwen220 commented on the issue:

[GitHub] incubator-eagle issue #309: [EAGLE-422] eagle support for mr & spark running...

Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/309 A sensitive message is found. Please remove that --- 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

Re: [Discuss] Check Style Specification

https://google.github.io/styleguide/javaguide.html - Hao On Mon, Aug 8, 2016 at 2:21 PM, Zhang, Edward (GDI Hadoop) < yonzh...@ebay.com> wrote: > It is nice. So do we have offline document for us to review Google java > style? > It is supposed that a lot of warnings will be generated with those

[GitHub] incubator-eagle issue #276: Updated code to support Druid Sum/Count Query

Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/276 @zombieJ , could you help 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 does not have this

[GitHub] incubator-eagle issue #310: Load app web classes and app topology classes us...

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/310 Merged into 'develop' 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 not have this feature

[jira] [Created] (EAGLE-427) Query startTime & endTime should support long

Zhao, Qingwen created EAGLE-427: --- Summary: Query startTime & endTime should support long Key: EAGLE-427 URL: https://issues.apache.org/jira/browse/EAGLE-427 Project: Eagle Issue Type:

[EAGLE BUILD FAILED] incubator-eagle-develop failed on build #9

The Apache Jenkins build system has built incubator-eagle-develop (build #9) Status: Failure Check console output at https://builds.apache.org/job/incubator-eagle-develop/9/ to view the results. Test Report is at: Test Result