HBase
  1. HBase
  2. HBASE-5122

Provide flexible method for loading ColumnInterpreters

    Details

    • Type: Task Task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      See the discussion on user list entitled 'AggregateProtocol Help'
      From Royston:

      I re-created my HBase table to contain Bytes.toBytes(Long) values and that fixed it.
      

      It was not the intention when AggregateProtocol was designed that users have to change their schema to match LongColumnInterpreter.

      This JIRA aims to provide a flexible way for users to load their custom ColumnInterpreters into region servers.

        Activity

        stack made changes -
        Fix Version/s 0.96.0 [ 12320040 ]
        Hide
        stack added a comment -

        Moving this task/improvement out of 0.96.0. Pull back if patch...

        Show
        stack added a comment - Moving this task/improvement out of 0.96.0. Pull back if patch...
        Lars Hofhansl made changes -
        Fix Version/s 0.96.0 [ 12320040 ]
        Fix Version/s 0.94.0 [ 12316419 ]
        Ted Yu made changes -
        Field Original Value New Value
        Fix Version/s 0.94.0 [ 12316419 ]
        Hide
        Ted Yu added a comment -

        An alternative is to associate custom jar files (containing, e.g., ColumnInterpreter implementations) with tables.
        Such association is expressed by a known table attribute.
        There is redundancy in this approach, but we don't need to create new container.

        Show
        Ted Yu added a comment - An alternative is to associate custom jar files (containing, e.g., ColumnInterpreter implementations) with tables. Such association is expressed by a known table attribute. There is redundancy in this approach, but we don't need to create new container.
        Hide
        Ted Yu added a comment -

        Since ColumnInterpreters aren't limited to specific tables, approach from HBASE-4554 cannot be used here.
        I thought of adding load method in RegionCoprocessorHost for ColumnInterpreters. But RegionCoprocessorHost only loads system and table coprocessors in its ctor.

        May need advice from coprocessor gurus about the proper solution.

        Show
        Ted Yu added a comment - Since ColumnInterpreters aren't limited to specific tables, approach from HBASE-4554 cannot be used here. I thought of adding load method in RegionCoprocessorHost for ColumnInterpreters. But RegionCoprocessorHost only loads system and table coprocessors in its ctor. May need advice from coprocessor gurus about the proper solution.
        Ted Yu created issue -

          People

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

            Dates

            • Created:
              Updated:

              Development