You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Hao Chen (JIRA)" <ji...@apache.org> on 2016/09/07 18:00:25 UTC

[jira] [Resolved] (EAGLE-520) Decouple Co-processor with Eagle Aggreation Query Service

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

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

> Decouple Co-processor with Eagle Aggreation Query Service
> ---------------------------------------------------------
>
>                 Key: EAGLE-520
>                 URL: https://issues.apache.org/jira/browse/EAGLE-520
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: v0.4.0
>            Reporter: Hao Chen
>            Assignee: Hao Chen
>             Fix For: v0.5.0
>
>
> h2. Done
> * Fix AggregateResultCallback test case
> * Fix configuration and Unit test on hbase
> * Support GenericInMemoryAggregateQuery when coprocessor is not enabled and faster-xml as default json library
> * Fix unit test: TestGenericServiceAPIResponseEntity
> * Fix coprocessor-based aggregation query.
> * Add Coprocessor integration test: CoprocessorITSuite
> * Add coprocessor tool: 
> {code}
> usage: java org.apache.eagle.storage.hbase.tools.CoprocessorTool
>             [--register/--unregister] [OPTIONS]
>  -config <arg>     Configuration file
>  -jar <arg>        Coprocessor target jar path
>  -localJar <arg>   Coprocessor local source jar path
>  -register         Register coprocessor
>  -table <arg>      HBase table name, separated with comma, for example,
>                    table1,table2,..
>  -unregister       Unregister coprocessor
> {code}



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