hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17397) AggregationClient cleanup
Date Sat, 31 Dec 2016 05:08:58 GMT

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

stack commented on HBASE-17397:
-------------------------------

You talking about this Aggregation endpoint [~vrodionov]?

Post evidence. Where was the issue? Yes, it is doing aggregations so I would expect it will
read lots of data doing its sums.

You want to discourage its use or purge this endpoint? Or I could move it to examples with
warning.  What should I warn folks against?

I don't have time to spend improving this implementation. I have higher priority tasks to
complete such as reviewing backup/restore.

> AggregationClient cleanup
> -------------------------
>
>                 Key: HBASE-17397
>                 URL: https://issues.apache.org/jira/browse/HBASE-17397
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>         Attachments: 17346.suggestion.txt
>
>
> AggregationClient is canonical coprocessor endpoint. It has some impurities spotted by
[~Apache9] over in HBASE-17346.



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

Mime
View raw message