HBase
  1. HBase
  2. HBASE-2416

provide support in UI for table export/import

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 0.20.1
    • Fix Version/s: None
    • Component/s: util
    • Labels:
      None

      Description

      It is desirable to provide HBase table export/import capability through table.jsp, similar to compaction/split buttons.

      For import/export button, an input field allows user to specify source/destination hdfs directory.

        Activity

        Hide
        Ted Yu added a comment -

        If no cluster is available, the import/export option should run local job (on HBase master node).

        Regards

        Show
        Ted Yu added a comment - If no cluster is available, the import/export option should run local job (on HBase master node). Regards
        Hide
        stack added a comment -

        .bq This enhancement is due to job tracker parameter not being in hbase-site.XML by default.

        Yeah, there is no need for hbase to know directly about MR clusters, only about the filesystem to use.

        .bq If hadoop cluster is available, user would specify job tracker parameter.

        If no cluster avaiable, the import/export option should be dimmed? Unavailable?

        .bq Commandline version of import/export can be enhanced to accept job tracker parameter as well for this scenario.

        I thought you could do this already? IIRC, Export/Import subclass hadoop Tool so you can pass *.xml config on command line.

        Show
        stack added a comment - .bq This enhancement is due to job tracker parameter not being in hbase-site.XML by default. Yeah, there is no need for hbase to know directly about MR clusters, only about the filesystem to use. .bq If hadoop cluster is available, user would specify job tracker parameter. If no cluster avaiable, the import/export option should be dimmed? Unavailable? .bq Commandline version of import/export can be enhanced to accept job tracker parameter as well for this scenario. I thought you could do this already? IIRC, Export/Import subclass hadoop Tool so you can pass *.xml config on command line.
        Hide
        Ted Yu added a comment -

        If hadoop cluster is available, user would specify job tracker parameter.
        Commandline version of import/export can be enhanced to accept job tracker parameter as well for this scenario.

        This enhancement is due to job tracker parameter not being in hbase-site.XML by default.

        Show
        Ted Yu added a comment - If hadoop cluster is available, user would specify job tracker parameter. Commandline version of import/export can be enhanced to accept job tracker parameter as well for this scenario. This enhancement is due to job tracker parameter not being in hbase-site.XML by default.
        Hide
        stack added a comment -

        Why should something like this be in the UI? Doesn't this issue also imply an hadoop cluster on standby ready to run the import/export? Or perhaps this feature is intended for small hbase installs only where not much data is involved?

        Show
        stack added a comment - Why should something like this be in the UI? Doesn't this issue also imply an hadoop cluster on standby ready to run the import/export? Or perhaps this feature is intended for small hbase installs only where not much data is involved?
        Hide
        Ted Yu added a comment -

        Field for Configuration setting, such as mapred.job.tracker, should also be provided so that the setting is only effective during import/export.
        Such setting would be passed to createSubmittableJob().

        Show
        Ted Yu added a comment - Field for Configuration setting, such as mapred.job.tracker, should also be provided so that the setting is only effective during import/export. Such setting would be passed to createSubmittableJob().

          People

          • Assignee:
            Unassigned
            Reporter:
            Ted Yu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development