FAQ
[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.

Search Discussions

  • Jim Kellerman (JIRA) at Aug 15, 2007 at 3:01 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Work on HADOOP-1711 started by Jim Kellerman.
    [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.
  • Jim Kellerman (JIRA) at Aug 15, 2007 at 6:23 pm
    [ 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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedAug 12, '07 at 5:00p
activeAug 15, '07 at 6:23p
posts3
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Jim Kellerman (JIRA): 3 posts

People

Translate

site design / logo © 2022 Grokbase