hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-1711) [hbase] HTable API should use interfaces instead of concrete classes as method parameters and return values
Date Wed, 15 Aug 2007 18:23:30 GMT

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

Jim Kellerman resolved HADOOP-1711.
-----------------------------------

    Resolution: Fixed

Built and tested on Fedora core 6 (dual processor) and Windows XP Pro (single processor)

Committed changes.

It turns out that the only API that had a non-interface parameter was HScanner.next, which
originally took a TreeMap. This was changed to SortedMap.

> [hbase] HTable API should use interfaces instead of concrete classes as method parameters
and return values
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1711
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1711
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/hbase
>    Affects Versions: 0.15.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.15.0
>
>
> Currently the HTable API uses concrete classes instead of interfaces, for example, TreeMap
instead of SortedMap or Map. The API should be revised to use interfaces instead so that clients
and the implementation is not bound to a specific concrete class.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message