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

stack updated HBASE-8101:
-------------------------

    Attachment: 8101.txt

Cleanup, findbugs fixes, and make it so illegal pass null row to Put/Delete, 
etc.

CatalogTracker -- just cleanup of whitespace and unused data members.
Action -- findbugs fix
Append -- Add check for null row and all passing of row, offset,length so 
easier working w/ Cells.
Delete -- ditto.  Throw new WrongRowException if not matching row.
Increment -- ditto plus findbugs and allow adding a Cell/KeyValue.
Get -- findbugs
Put -- ditto
HBaseAdmin -- javadoc warning fixes.
RwoMutations -- findbugs
WrongRowException -- new exception if Cell row does not match that of the Put, 
Delete, etc. host
NullComparator -- findbugs
AuthMethod -- make valueOf public.. need to look at it down in ipc
CellComparator -- findbugs
KeyValue -- findbugs
CellCodec/BaseDecoder/BaseEncoder -- make accessible from other packages
ByteBufferOutputStream -- move to hbase-common and into io package.
DiffKeyDeltaEncoder -- findbugs
Bytes -- add copy method.
TestPutDeleteEtcCellIteration -- tests to Iterate Cells.
                
> Cleanup: findbugs and javadoc warning fixes as well as making it illegal 
> passing null row to Put/Delete, etc.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8101
>                 URL: https://issues.apache.org/jira/browse/HBASE-8101
>             Project: HBase
>          Issue Type: Sub-task
>          Components: IPC/RPC
>            Reporter: stack
>             Fix For: 0.95.0
>
>         Attachments: 8101.txt
>
>
> Part of hbase-7900 broken out so that patch gets smaller.  This is a patch 
> with cleanup mostly findbugs fixes (general ones) as well as adding check for 
> null row being passed to Put, Get, etc.  This patch helps rpc along.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to