[jira] [Commented] (EAGLE-366) Create HBase tables if not exists in Eagle 0.5

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372213#comment-15372213 ] ASF GitHub Bot commented on EAGLE-366: -- GitHub user qingwen220 opened a pull request:

[GitHub] incubator-eagle pull request #264: EAGLE-366: Create HBase tables if not exi...

2016-07-11 Thread qingwen220
GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/264 EAGLE-366: Create HBase tables if not exists in Eagle 0.5 https://issues.apache.org/jira/browse/EAGLE-366 You can merge this pull request into a Git repository by running: $ git

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

2016-07-11 Thread Hao Chen
+1 (binding) Invalid JAR files issue reported in previous apache-eagle-0.4.0-incubating rc2 have been resolved. * Downloaded & Built successfully on MacOSX 10.10.5 with Java HotSpot 1.7.0_75. * Verified signature * Ran rat:check and passed - Hao On Tue, Jul 12, 2016 at 6:39 AM, Lu, Huizhi

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

2016-07-11 Thread Lu, Huizhi
+1 (non-binding) * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X * Signature checked, md5, sha1 verified * Apache rat:check passed (mvn apache-rat:check) * Release matches tag. -Huizhi > On Jul 11, 2016, at 2:40 AM, Michael Wu wrote: > > Hi all, > >

[GitHub] incubator-eagle pull request #260: EAGLE-350: Running queue metrics monitori...

2016-07-11 Thread qingwen220
Github user qingwen220 closed the pull request at: https://github.com/apache/incubator-eagle/pull/260 --- 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

[GitHub] incubator-eagle pull request #261: EAGLE-357. Fix building fail when jshint.

2016-07-11 Thread pkuwm
Github user pkuwm closed the pull request at: https://github.com/apache/incubator-eagle/pull/261 --- 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-357) Building failed: at eagle-webservice app/public/feature/common/controller.js

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372126#comment-15372126 ] ASF GitHub Bot commented on EAGLE-357: -- Github user pkuwm closed the pull request at:

[jira] [Resolved] (EAGLE-276) JPM - Spark job history monitoring

2016-07-11 Thread wujinhu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu resolved EAGLE-276. --- Resolution: Fixed > JPM - Spark job history monitoring > - > >

[jira] [Closed] (EAGLE-276) JPM - Spark job history monitoring

2016-07-11 Thread wujinhu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-276. - > JPM - Spark job history monitoring > - > > Key: EAGLE-276 >

[GitHub] incubator-eagle pull request #217: EAGLE-276 eagle support for mr & spark hi...

2016-07-11 Thread wujinhu
Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/217 --- 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-276) JPM - Spark job history monitoring

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372093#comment-15372093 ] ASF GitHub Bot commented on EAGLE-276: -- Github user wujinhu closed the pull request at:

[jira] [Closed] (EAGLE-361) Fix test building problem caused by kafka version and remove unused files

2016-07-11 Thread wujinhu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-361. - fixed > Fix test building problem caused by kafka version and remove unused files >

[jira] [Commented] (EAGLE-350) Running queue metrics monitoring

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372070#comment-15372070 ] ASF GitHub Bot commented on EAGLE-350: -- Github user qingwen220 commented on the issue:

[GitHub] incubator-eagle issue #260: EAGLE-350: Running queue metrics monitoring

2016-07-11 Thread qingwen220
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/260 This feature must configure Hbase as the storage --- 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

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372026#comment-15372026 ] Edward Zhang commented on EAGLE-371: [~julianhyde]maybe your concern is we should maintain eagle

[jira] [Closed] (EAGLE-357) Building failed: at eagle-webservice app/public/feature/common/controller.js

2016-07-11 Thread Huizhi Lu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huizhi Lu closed EAGLE-357. --- Resolution: Fixed Fix Version/s: (was: v0.4.0) v0.3.1 Fixed and merged. >

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372017#comment-15372017 ] Edward Zhang commented on EAGLE-371: [~julianhyde] we have eagle document well maintained in

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread Julian Hyde (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372004#comment-15372004 ] Julian Hyde commented on EAGLE-371: --- Does this mean that eagle-docs are being removed from Apache git?

[jira] [Commented] (EAGLE-366) Create HBase tables if not exists in Eagle 0.5

2016-07-11 Thread Hao Chen (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372001#comment-15372001 ] Hao Chen commented on EAGLE-366: [~yonzhang2012] For hbase tables, we could use the feature here

[jira] [Resolved] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Zhang resolved EAGLE-371. Resolution: Fixed merged > remove eagle-docs from develop branch >

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371980#comment-15371980 ] ASF GitHub Bot commented on EAGLE-371: -- Github user yonzhang commented on the issue:

[jira] [Closed] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Zhang closed EAGLE-371. -- > remove eagle-docs from develop branch > - > > Key:

[GitHub] incubator-eagle pull request #263: EAGLE-371 remove eagle-docs from develop ...

2016-07-11 Thread yonzhang
Github user yonzhang closed the pull request at: https://github.com/apache/incubator-eagle/pull/263 --- 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-371) remove eagle-docs from develop branch

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371981#comment-15371981 ] ASF GitHub Bot commented on EAGLE-371: -- Github user yonzhang closed the pull request at:

[GitHub] incubator-eagle issue #263: EAGLE-371 remove eagle-docs from develop branch

2016-07-11 Thread yonzhang
Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/263 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

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371966#comment-15371966 ] ASF GitHub Bot commented on EAGLE-371: -- GitHub user yonzhang opened a pull request:

[GitHub] incubator-eagle pull request #263: EAGLE-371 remove eagle-docs from develop ...

2016-07-11 Thread yonzhang
GitHub user yonzhang opened a pull request: https://github.com/apache/incubator-eagle/pull/263 EAGLE-371 remove eagle-docs from develop branch remove eagle-docs from develop branch Author: Yong Zhang Reviewer: Yong Zhang Closes: #371

[jira] [Created] (EAGLE-371) remove eagle-docs from develop branch

2016-07-11 Thread Edward Zhang (JIRA)
Edward Zhang created EAGLE-371: -- Summary: remove eagle-docs from develop branch Key: EAGLE-371 URL: https://issues.apache.org/jira/browse/EAGLE-371 Project: Eagle Issue Type: Improvement

[jira] [Commented] (EAGLE-350) Running queue metrics monitoring

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371940#comment-15371940 ] ASF GitHub Bot commented on EAGLE-350: -- Github user qingwen220 commented on the issue:

[GitHub] incubator-eagle issue #260: EAGLE-350: Running queue metrics monitoring

2016-07-11 Thread qingwen220
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/260 Thanks! You are right. `dataJoinPollIntervalSec` configuration in the configuration file is useless in this feature. i will remove it. --- If your project is set up

[jira] [Closed] (EAGLE-370) Absence alert engine

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Zhang closed EAGLE-370. -- Resolution: Fixed merge with pr 262 > Absence alert engine > > >

[GitHub] incubator-eagle pull request #262: absence alert engine

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

[GitHub] incubator-eagle issue #262: absence alert engine

2016-07-11 Thread yonzhang
Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/262 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

[jira] [Created] (EAGLE-370) Absence alert engine

2016-07-11 Thread Edward Zhang (JIRA)
Edward Zhang created EAGLE-370: -- Summary: Absence alert engine Key: EAGLE-370 URL: https://issues.apache.org/jira/browse/EAGLE-370 Project: Eagle Issue Type: Improvement Affects Versions:

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

2016-07-11 Thread Huizhi Lu
+1 (non-binding) * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X * Signature checked, md5, sha1 verified * Apache rat:check passed (mvn apache-rat:check) * Release matches tag. -Huizhi > On Jul 11, 2016, at 2:40 AM, Michael Wu wrote: > > Hi all, > >

[GitHub] incubator-eagle pull request #262: absence alert engine

2016-07-11 Thread yonzhang
GitHub user yonzhang opened a pull request: https://github.com/apache/incubator-eagle/pull/262 absence alert engine You can merge this pull request into a Git repository by running: $ git pull https://github.com/yonzhang/incubator-eagle develop Alternatively you can review

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

2016-07-11 Thread Julian Hyde
Downloaded, checked license, notice, signatures, built on OS X JDK 1.7. Checked that the JARs have gone. +1 (binding) Julian > On Jul 11, 2016, at 2:40 AM, Michael Wu wrote: > > Hi all, > > This is a release vote for Apache Eagle, version 0.4.0-incubating, release >

[jira] [Commented] (EAGLE-357) Building failed: at eagle-webservice app/public/feature/common/controller.js

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371358#comment-15371358 ] ASF GitHub Bot commented on EAGLE-357: -- Github user yonzhang commented on the issue:

[GitHub] incubator-eagle issue #261: EAGLE-357. Fix building fail when jshint.

2016-07-11 Thread yonzhang
Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/261 looks good fix --- 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

[jira] [Commented] (EAGLE-357) Building failed: at eagle-webservice app/public/feature/common/controller.js

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371345#comment-15371345 ] ASF GitHub Bot commented on EAGLE-357: -- GitHub user pkuwm opened a pull request:

[GitHub] incubator-eagle pull request #261: EAGLE-357. Fix building fail when jshint.

2016-07-11 Thread pkuwm
GitHub user pkuwm opened a pull request: https://github.com/apache/incubator-eagle/pull/261 EAGLE-357. Fix building fail when jshint. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pkuwm/incubator-eagle EAGLE-357 Alternatively

[jira] [Commented] (EAGLE-366) Create HBase tables if not exists in Eagle 0.5

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371232#comment-15371232 ] Edward Zhang commented on EAGLE-366: [~qingwzhao][~haoch] in 0.5 how do we handle table creation for

[jira] [Commented] (EAGLE-368) JSlint failed in common/controller.js

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371205#comment-15371205 ] Edward Zhang commented on EAGLE-368: In which version is this happening and in which version do we want

[jira] [Commented] (EAGLE-369) Improve eagle alert email template to provide more useful information and user experience

2016-07-11 Thread Edward Zhang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371201#comment-15371201 ] Edward Zhang commented on EAGLE-369: I would suggest to let user to edit template as they like, but

[VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

2016-07-11 Thread Michael Wu
Hi all, This is a release vote for Apache Eagle, version 0.4.0-incubating, release candidate 3. Highlighted changes in this release are as the following: * JBDC Metadata Storage Extension * Topology management in remote mode including start/stop/status operations * Auditlogparser for

[GitHub] incubator-eagle pull request #260: EAGLE-350: Running queue metrics monitori...

2016-07-11 Thread qingwen220
GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/260 EAGLE-350: Running queue metrics monitoring https://issues.apache.org/jira/browse/EAGLE-350 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (EAGLE-350) Running queue metrics monitoring

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370455#comment-15370455 ] ASF GitHub Bot commented on EAGLE-350: -- GitHub user qingwen220 opened a pull request:

[jira] [Created] (EAGLE-369) Improve eagle alert email template to provide more useful information and user experience

2016-07-11 Thread Su Ralph (JIRA)
Su Ralph created EAGLE-369: -- Summary: Improve eagle alert email template to provide more useful information and user experience Key: EAGLE-369 URL: https://issues.apache.org/jira/browse/EAGLE-369 Project:

[jira] [Resolved] (EAGLE-368) JSlint failed in common/controller.js

2016-07-11 Thread Jilin, Jiang (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-368. Resolution: Fixed > JSlint failed in common/controller.js > - >

[jira] [Commented] (EAGLE-355) UI advanced policy expression can't parse

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370372#comment-15370372 ] ASF GitHub Bot commented on EAGLE-355: -- Github user anyway1021 commented on the issue:

[GitHub] incubator-eagle issue #251: EAGLE-355 fix advanced sql parse logic

2016-07-11 Thread anyway1021
Github user anyway1021 commented on the issue: https://github.com/apache/incubator-eagle/pull/251 LGTM Verified on my local, it's built successfully now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

Re: [Discuss] what will be the decent way to remove jars from source code for releases

2016-07-11 Thread Julian Hyde
Can someone explain why these jar files have to be checked into git? Many other jar (and other binary) files are retrieved from a maven repo when you build; why not these? You can use maven magic to extract/filter/copy these files exactly where you need them on the first build. Source files have

[jira] [Created] (EAGLE-368) JSlint failed in common/controller.js

2016-07-11 Thread Jilin, Jiang (JIRA)
Jilin, Jiang created EAGLE-368: -- Summary: JSlint failed in common/controller.js Key: EAGLE-368 URL: https://issues.apache.org/jira/browse/EAGLE-368 Project: Eagle Issue Type: Bug

[jira] [Closed] (EAGLE-367) update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356

2016-07-11 Thread Michael Wu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-367. Resolution: Done > update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356 >

[GitHub] incubator-eagle pull request #259: [EAGLE-367] update CHANGELOG.txt appendin...

2016-07-11 Thread anyway1021
Github user anyway1021 closed the pull request at: https://github.com/apache/incubator-eagle/pull/259 --- 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-367) update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370307#comment-15370307 ] ASF GitHub Bot commented on EAGLE-367: -- Github user anyway1021 closed the pull request at:

[jira] [Commented] (EAGLE-367) update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370300#comment-15370300 ] ASF GitHub Bot commented on EAGLE-367: -- Github user qingwen220 commented on the issue:

[GitHub] incubator-eagle issue #259: [EAGLE-367] update CHANGELOG.txt appending bug-i...

2016-07-11 Thread qingwen220
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/259 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or

[jira] [Commented] (EAGLE-367) update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356

2016-07-11 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370297#comment-15370297 ] ASF GitHub Bot commented on EAGLE-367: -- GitHub user anyway1021 opened a pull request:

[GitHub] incubator-eagle pull request #259: [EAGLE-367] update CHANGELOG.txt appendin...

2016-07-11 Thread anyway1021
GitHub user anyway1021 opened a pull request: https://github.com/apache/incubator-eagle/pull/259 [EAGLE-367] update CHANGELOG.txt appending bug-info of: EAGLE-355, EAGLE-356 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (EAGLE-355) UI advanced policy expression can't parse

2016-07-11 Thread Michael Wu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu updated EAGLE-355: - Fix Version/s: v0.4.0 > UI advanced policy expression can't parse >

[jira] [Created] (EAGLE-367) update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356

2016-07-11 Thread Michael Wu (JIRA)
Michael Wu created EAGLE-367: Summary: update CHANGELOG.txt for 0.4.0 release, picking EAGLE-355 and EAGLE-356 Key: EAGLE-367 URL: https://issues.apache.org/jira/browse/EAGLE-367 Project: Eagle

[jira] [Created] (EAGLE-366) Create HBase tables if not exists in Eagle 0.5

2016-07-11 Thread Zhao, Qingwen (JIRA)
Zhao, Qingwen created EAGLE-366: --- Summary: Create HBase tables if not exists in Eagle 0.5 Key: EAGLE-366 URL: https://issues.apache.org/jira/browse/EAGLE-366 Project: Eagle Issue Type:

[jira] [Reopened] (EAGLE-365) Fix found issues of 0.4.0-incubating-rc2 and create rc3

2016-07-11 Thread Michael Wu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu reopened EAGLE-365: -- > Fix found issues of 0.4.0-incubating-rc2 and create rc3 >

New release branch created: branch-0.4.0

2016-07-11 Thread Michael Wu
Hi all, In order not to bring adverse impact to those who continuously contribute upon branch "branch-0.4", and also for the sake of fixing issues found in voting of apache-eagle-0.4.0-incubating-rc2, I've just created new release branch "branch-0.4.0" for upcoming 0.4.0-incubating release.

[jira] [Closed] (EAGLE-365) Fix found issues of 0.4.0-incubating-rc2 and create rc3

2016-07-11 Thread Michael Wu (JIRA)
[ https://issues.apache.org/jira/browse/EAGLE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-365. Resolution: Won't Fix > Fix found issues of 0.4.0-incubating-rc2 and create rc3 >

[GitHub] incubator-eagle pull request #258: Eagle 365 solve issues found in release v...

2016-07-11 Thread anyway1021
Github user anyway1021 closed the pull request at: https://github.com/apache/incubator-eagle/pull/258 --- 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

[GitHub] incubator-eagle issue #258: Eagle 365 solve issues found in release vote for...

2016-07-11 Thread anyway1021
Github user anyway1021 commented on the issue: https://github.com/apache/incubator-eagle/pull/258 I totally agree with you, let me close this PR and have a try. --- 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