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

add per-table/per-cf configuration via metadata

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Umbrella
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.95.2
    • 0.95.0
    • None
    • Hide
      The ability to configure most configuration parameters per column family or table. The column family configuration overrules table configuration, which in turn overrides xml configuration. The column family metadata that was previously used still overrides any configuration.

      To set configuration, you can use shell commands (see also help 'create', help 'alter'); example:
      alter 'mytable', CONFIGURATION => {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}
      alter 'mytable', {NAME => 'mycolumnfamily', CONFIGURATION => {'hbase.hstore.blockingStoreFiles' => '10'}}

      You can also do it programmatically by modifying HTableDescriptor and HColumnDescriptor for create and alter operations (setConfiguration method).
      Show
      The ability to configure most configuration parameters per column family or table. The column family configuration overrules table configuration, which in turn overrides xml configuration. The column family metadata that was previously used still overrides any configuration. To set configuration, you can use shell commands (see also help 'create', help 'alter'); example: alter 'mytable', CONFIGURATION => {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'} alter 'mytable', {NAME => 'mycolumnfamily', CONFIGURATION => {'hbase.hstore.blockingStoreFiles' => '10'}} You can also do it programmatically by modifying HTableDescriptor and HColumnDescriptor for create and alter operations (setConfiguration method).

    Description

      Regardless of the compaction policy, it makes sense to have separate configuration for compactions for different tables and column families, as their access patterns and workloads can be different. In particular, for tiered compactions that are being ported from 0.89-fb branch it is necessary to have, to use it properly.
      We might want to add support for compaction configuration via metadata on table/cf.

      Attachments

        1. HBASE-7236-PROTOTYPE.patch
          38 kB
          Sergey Shelukhin
        2. HBASE-7236-PROTOTYPE.patch
          62 kB
          Sergey Shelukhin
        3. HBASE-7236-PROTOTYPE-v1.patch
          43 kB
          Sergey Shelukhin
        4. HBASE-7236-v0.patch
          148 kB
          Sergey Shelukhin
        5. HBASE-7236-v1.patch
          149 kB
          Sergey Shelukhin
        6. HBASE-7236-v2.patch
          151 kB
          Sergey Shelukhin
        7. HBASE-7236-v3.patch
          151 kB
          Sergey Shelukhin
        8. HBASE-7236-v4.patch
          288 kB
          Sergey Shelukhin
        9. HBASE-7236-v5.patch
          220 kB
          Sergey Shelukhin
        10. HBASE-7236-v6.patch
          221 kB
          Sergey Shelukhin
        11. HBASE-7236-v6.patch
          221 kB
          Sergey Shelukhin

        Issue Links

        There are no Sub-Tasks for this issue.

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            sershe Sergey Shelukhin
            sershe Sergey Shelukhin
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment