[
https://issues.apache.org/jira/browse/TRAFODION-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698015#comment-14698015
]
Selvaganesan Govindarajan edited comment on TRAFODION-1422 at 8/17/15 2:13 PM:
-------------------------------------------------------------------------------
Many methods from HTableClient_JNI class are moved to HBaseClient_JNI.
HTableClient_JNI::deleteRow method is left around because it is being used by
ExpHBaseInterface_JNI::deleteColumns method. When this code is optimized and if
HTableClient_JNI::deleteRow is not used, please consider deleting this method
from HTableClient_JNI because there is no other caller to this method.
was (Author: selvag):
Many methods from HTableClient_JNI class is moved to HBaseClient_JNI.
HTableClient_JNI::deleteRow method is left around because it is being used by
ExpHBaseInterface_JNI::deleteColumns method. When this code is optimized and if
HTableClient_JNI::deleteRow is not used, please consider deleting this method
from HTableClient_JNI because there is no other caller to this method.
> Delete column can be dramatically improved (ALTER statement)
> ------------------------------------------------------------
>
> Key: TRAFODION-1422
> URL: https://issues.apache.org/jira/browse/TRAFODION-1422
> Project: Apache Trafodion
> Issue Type: Improvement
> Reporter: Eric Owhadi
> Priority: Minor
> Labels: performance
> Fix For: 2.0-incubating
>
>
> The current code path for delete column has not been optimized and can be
> greatly improved. See comments bellow for many ways to implement optimization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
