[jira] [Commented] (EAGLE-283) Convert fid,uid in MapR's audit log to FIle/folder name, user name

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

[GitHub] incubator-eagle pull request #321: EAGLE-283: Convert fid,uid in MapR's audi...

GitHub user DadanielZ opened a pull request: https://github.com/apache/incubator-eagle/pull/321 EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user name 1. Added resolver for user's input of "volume", "file/folder", "Status" - These resolver provide

[jira] [Updated] (EAGLE-442) Support to extend metastore DAO modules in SPI

[ https://issues.apache.org/jira/browse/EAGLE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-442: --- Labels: app-framework extensibility (was: app-framework) > Support to extend metastore DAO modules in SPI >

[jira] [Updated] (EAGLE-442) Support to extend metastore DAO modules in SPI

[ https://issues.apache.org/jira/browse/EAGLE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-442: --- Affects Version/s: v0.5.0 > Support to extend metastore DAO modules in SPI >

[jira] [Created] (EAGLE-442) Support to extend metastore DAO modules in SPI

Hao Chen created EAGLE-442: -- Summary: Support to extend metastore DAO modules in SPI Key: EAGLE-442 URL: https://issues.apache.org/jira/browse/EAGLE-442 Project: Eagle Issue Type: Sub-task

[jira] [Updated] (EAGLE-442) Support to extend metastore DAO modules in SPI

[ https://issues.apache.org/jira/browse/EAGLE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-442: --- Labels: app-framework (was: ) > Support to extend metastore DAO modules in SPI >

[jira] [Commented] (EAGLE-441) Combine environment configuration into application configuration for execution

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

[jira] [Updated] (EAGLE-441) Combine environment configuration into application configuration for execution

[ https://issues.apache.org/jira/browse/EAGLE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-441: --- Affects Version/s: v0.5.0 > Combine environment configuration into application configuration for execution >

[GitHub] incubator-eagle pull request #320: EAGLE-441 AppConfig will override EnvConf...

GitHub user haoch opened a pull request: https://github.com/apache/incubator-eagle/pull/320 EAGLE-441 AppConfig will override EnvConfig and EnvConfig is default config https://issues.apache.org/jira/browse/EAGLE-441 You can merge this pull request into a Git repository by running:

[jira] [Commented] (EAGLE-441) Combine environment configuration into application configuration for execution

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

[jira] [Updated] (EAGLE-441) Combine environment configuration into application configuration for execution

[ https://issues.apache.org/jira/browse/EAGLE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-441: --- Labels: app-framework (was: ) > Combine environment configuration into application configuration for

[GitHub] incubator-eagle pull request #314: EAGLE-436 Decouple Application Class-base...

Github user haoch closed the pull request at: https://github.com/apache/incubator-eagle/pull/314 --- 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-436) Decouple Application Class-based Configuration

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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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

[GitHub] incubator-eagle pull request #319: [EAGLE-439] Introduce policy enable/disab...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/319 --- 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-435) Coordiantor schedule operation must be exclusive in distributed deployment

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

[jira] [Commented] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

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

[GitHub] incubator-eagle issue #317: [EAGLE-435] make coordiantor schedule operation ...

Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/317 Looks only fix the listener wise. The intension is to guarantee all the schedule.build(), not only the listener. --- If your project is set up for it, you can reply to this email and have

[GitHub] incubator-eagle issue #317: [EAGLE-435] make coordiantor schedule operation ...

Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/317 Looks only fix the listener wise. The intension is to guarantee all the schedule.build(), not only the listener. --- If your project is set up for it, you can reply to this email and have

[jira] [Created] (EAGLE-440) Alert mongodb storage refine

ZengMing created EAGLE-440: -- Summary: Alert mongodb storage refine Key: EAGLE-440 URL: https://issues.apache.org/jira/browse/EAGLE-440 Project: Eagle Issue Type: Improvement Reporter:

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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

[GitHub] incubator-eagle pull request #319: [EAGLE-439] Introduce policy enable/disab...

GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/319 [EAGLE-439] Introduce policy enable/disable support You can merge this pull request into a Git repository by running: $ git pull https://github.com/garrettlish/incubator-eagle

[GitHub] incubator-eagle pull request #318: [EAGLE-439] Introduce policy enable/disab...

Github user garrettlish closed the pull request at: https://github.com/apache/incubator-eagle/pull/318 --- 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-439) Introduce policy enable/disable support

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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

[ https://issues.apache.org/jira/browse/EAGLE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414533#comment-15414533 ] ASF GitHub Bot commented on EAGLE-439: -- Github user RalphSu commented on a diff in the pull request:

[GitHub] incubator-eagle pull request #318: [EAGLE-439] Introduce policy enable/disab...

Github user RalphSu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/318#discussion_r74170914 --- Diff: eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/engine/coordinator/PolicyDefinition.java ---

[GitHub] incubator-eagle pull request #313: [EAGLE-434] fix policy change listener da...

Github user garrettlish closed the pull request at: https://github.com/apache/incubator-eagle/pull/313 --- 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-434) BUG: periodically trigger schedule in service mode

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

[jira] [Commented] (EAGLE-439) Introduce policy enable/disable support

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

[GitHub] incubator-eagle pull request #318: [EAGLE-439] Introduce policy enable/disab...

GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/318 [EAGLE-439] Introduce policy enable/disable support You can merge this pull request into a Git repository by running: $ git pull https://github.com/garrettlish/incubator-eagle

[jira] [Created] (EAGLE-439) Introduce policy enable/disable support

Garrett Li created EAGLE-439: Summary: Introduce policy enable/disable support Key: EAGLE-439 URL: https://issues.apache.org/jira/browse/EAGLE-439 Project: Eagle Issue Type: Improvement

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

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

[GitHub] incubator-eagle issue #316: [EAGLE-438] Multiple Inputs for Hadoop JMX Colle...

Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/316 otherwise, looks good to me. +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[ https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414453#comment-15414453 ] ASF GitHub Bot commented on EAGLE-438: -- Github user RalphSu commented on a diff in the pull request:

[GitHub] incubator-eagle pull request #316: [EAGLE-438] Multiple Inputs for Hadoop JM...

Github user RalphSu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/316#discussion_r74164639 --- Diff: eagle-external/hadoop_jmx_collector/config-sample.json --- @@ -12,18 +12,35 @@ "https":false } }, -

[GitHub] incubator-eagle pull request #316: [EAGLE-438] Multiple Inputs for Hadoop JM...

GitHub user peterkim95 opened a pull request: https://github.com/apache/incubator-eagle/pull/316 [EAGLE-438] Multiple Inputs for Hadoop JMX Collector Python Script https://issues.apache.org/jira/browse/EAGLE-438 You can merge this pull request into a Git repository by running:

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

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

[jira] [Comment Edited] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[ https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414313#comment-15414313 ] Peter Kim edited comment on EAGLE-438 at 8/9/16 10:02 PM: -- Yes, in the config.json

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[ https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414313#comment-15414313 ] Peter Kim commented on EAGLE-438: - Yes, in the config.json file that the script uses, the inputs will be an

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[ https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414305#comment-15414305 ] Edward Zhang commented on EAGLE-438: [~senthilec566] I think we already have resource manager related

[jira] [Created] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

Peter Kim created EAGLE-438: --- Summary: Multiple Inputs for Hadoop JMX Collector Python Script Key: EAGLE-438 URL: https://issues.apache.org/jira/browse/EAGLE-438 Project: Eagle Issue Type: New

[jira] [Created] (EAGLE-437) create workable fat jar for starting application remotely

Edward Zhang created EAGLE-437: -- Summary: create workable fat jar for starting application remotely Key: EAGLE-437 URL: https://issues.apache.org/jira/browse/EAGLE-437 Project: Eagle Issue

[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=15414218#comment-15414218 ] Edward Zhang commented on EAGLE-430: We should think about fat jar packaging process. When we package,

[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=15414188#comment-15414188 ] ASF GitHub Bot commented on EAGLE-430: -- GitHub user yonzhang opened a pull request:

[GitHub] incubator-eagle pull request #315: explore new packaging method for eagle us...

GitHub user yonzhang opened a pull request: https://github.com/apache/incubator-eagle/pull/315 explore new packaging method for eagle using new app framework https://issues.apache.org/jira/browse/EAGLE-430 You can merge this pull request into a Git repository by running: $ git

[jira] [Commented] (EAGLE-436) Decouple Application Class-based Configuration

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

[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=15414150#comment-15414150 ] ASF GitHub Bot commented on EAGLE-428: -- Github user yonzhang closed the pull request at:

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

Github user yonzhang closed the pull request at: https://github.com/apache/incubator-eagle/pull/312 --- 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 #314: EAGLE-436 Decouple Application Class-based Confi...

Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/314 Good refinement, good to go --- 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

[GitHub] incubator-eagle issue #312: Hbase monitoring metadata browse API in new app ...

Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/312 That is obvious. Again this is to make first use case to work, I will leave this change to app framework refine. --- If your project is set up for it, you can reply to this email and have

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

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

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/312#discussion_r74025706 --- Diff: eagle-server/src/main/resources/application.conf --- @@ -42,6 +42,7 @@ "metadata":{ "store":

[GitHub] incubator-eagle pull request #314: EAGLE-436 Decouple Application Class-base...

GitHub user haoch opened a pull request: https://github.com/apache/incubator-eagle/pull/314 EAGLE-436 Decouple Application Class-based Configuration https://issues.apache.org/jira/browse/EAGLE-436 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (EAGLE-436) Decouple Application Class-based Configuration

Hao Chen created EAGLE-436: -- Summary: Decouple Application Class-based Configuration Key: EAGLE-436 URL: https://issues.apache.org/jira/browse/EAGLE-436 Project: Eagle Issue Type: New Feature

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

Github user RalphSu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/312#discussion_r74022788 --- Diff: eagle-server/src/main/resources/application.conf --- @@ -42,6 +42,7 @@ "metadata":{ "store":

[GitHub] incubator-eagle pull request #312: Hbase monitoring metadata browse API in n...

Github user haoch commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/312#discussion_r74021223 --- Diff: eagle-server/src/main/resources/application.conf --- @@ -42,6 +42,7 @@ "metadata":{ "store":

[GitHub] incubator-eagle issue #312: Hbase monitoring metadata browse API in new app ...

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/312 LGTM, except: 1. MetadataDaoFactory, but we could refactor this later 2. Prefer to rename configuration key "connection" as "metadata.connection" If we want to use

[jira] [Assigned] (EAGLE-434) BUG: periodically trigger schedule in service mode

[ https://issues.apache.org/jira/browse/EAGLE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li reassigned EAGLE-434: Assignee: Garrett Li > BUG: periodically trigger schedule in service mode >

[jira] [Commented] (EAGLE-434) BUG: periodically trigger schedule in service mode

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

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

[ https://issues.apache.org/jira/browse/EAGLE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-435: --- Affects Version/s: v0.5.0 > Coordiantor schedule operation must be exclusive in distributed deployment >

[GitHub] incubator-eagle issue #313: [EAGLE-434] fix policy change listener daemon no...

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/313 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 if

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

[ https://issues.apache.org/jira/browse/EAGLE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-435: --- Fix Version/s: v0.5.0 > Coordiantor schedule operation must be exclusive in distributed deployment >

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

[ https://issues.apache.org/jira/browse/EAGLE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-435: --- Assignee: Garrett Li > Coordiantor schedule operation must be exclusive in distributed deployment >

Re: Request EAGLE JIRA assignee permission

Garrett, it's done, pls. have a try. - Hao On Tue, Aug 9, 2016 at 4:07 PM, Garrett Li wrote: > Hi all, > > > This is Garrett Li, I am going to work on UMP alerting part, I would like > to request EAGLE JIRA assignee permission, my account in issues.apache.org > is

Request EAGLE JIRA assignee permission

Hi all, This is Garrett Li, I am going to work on UMP alerting part, I would like to request EAGLE JIRA assignee permission, my account in issues.apache.org is garrettlish (garrettl...@163.com). Thanks a lot! Thanks, Garrett

[jira] [Updated] (EAGLE-435) Coordiantor schedule operation must be exclusive in distributed deployment

[ https://issues.apache.org/jira/browse/EAGLE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-435: - Issue Type: Improvement (was: Bug) Summary: Coordiantor schedule operation must be exclusive in

[jira] [Created] (EAGLE-435) Enhancement: coordiantor schedule operation must be exclusive in distributed deployment

Garrett Li created EAGLE-435: Summary: Enhancement: coordiantor schedule operation must be exclusive in distributed deployment Key: EAGLE-435 URL: https://issues.apache.org/jira/browse/EAGLE-435 Project:

[jira] [Commented] (EAGLE-434) BUG: periodically trigger schedule in service mode

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

[GitHub] incubator-eagle pull request #313: [EAGLE-434] fix policy change listener da...

GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/313 [EAGLE-434] fix policy change listener daemon not working issue You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (EAGLE-434) BUG: periodically trigger schedule in service mode

[ https://issues.apache.org/jira/browse/EAGLE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-434: - Labels: alert_engine (was: ) > BUG: periodically trigger schedule in service mode >

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15413154#comment-15413154 ] Chang chen commented on EAGLE-411: -- [~haoch] Sure > Refactor hbase related unit test cases with mockito

[jira] [Updated] (EAGLE-427) Query startTime & endTime should support timestamp

[ https://issues.apache.org/jira/browse/EAGLE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-427: Summary: Query startTime & endTime should support timestamp (was: Query startTime & endTime should

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

[ https://issues.apache.org/jira/browse/EAGLE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-433: --- Labels: contributers-welcome (was: ) > DropWizard Service Security Integration with Basic Auth & LDAP >

[jira] [Commented] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15413012#comment-15413012 ] Hao Chen commented on EAGLE-411: [~baibaichen] could you please let your team start with this ticket about

[jira] [Updated] (EAGLE-411) Refactor hbase related unit test cases with mockito and mini-hbase

[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-411: --- Assignee: Chang chen (was: JiJun Tang) > Refactor hbase related unit test cases with mockito and mini-hbase >

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

[ https://issues.apache.org/jira/browse/EAGLE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-433: --- Description: Eagle Authentication should support Basic Auth and integrate with: * Configure file based

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

[ https://issues.apache.org/jira/browse/EAGLE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-433: --- Fix Version/s: v0.5.0 > DropWizard Service Security Integration with Basic Auth & LDAP >

[jira] [Updated] (EAGLE-433) DropWizard Service Security Integration with Basic Auth & LDAP

[ https://issues.apache.org/jira/browse/EAGLE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-433: --- Affects Version/s: v0.5.0 > DropWizard Service Security Integration with Basic Auth & LDAP >