Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-2036

Use Configuration instead of HBaseConfiguration

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.90.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      HBaseConfiguration as an object is now deprecated. Use HBaseConfiguration.create to make an Hadoop Configuration populated with hbase config. from here on out.

      Description

      HBaseConfiguration extends Configuration but does not add any functionality to it. The only function is hashCode() which really should be refactored into Hadoop Configuration.
      I think in all the places(especially in the client side) HBase methods and classes should accept Configuration rather than HBaseConfiguration. The creation of the configuration with the right files (hbase-site and hbase-default) should not be encapsulated in a private method, but in a public static one.

      The issues has arisen in our nutch+hbase patch for which we include both nutch configuration and hbase configurations. Moreover people may want to include separate project-specific configuration files to their configurations without the need to be dependent on the HBaseConfiguration.

        Attachments

        1. hconf_v1.patch
          89 kB
          Enis Soztutar
        2. hconf.patch
          81 kB
          Enis Soztutar

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              enis Enis Soztutar
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: