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

Addition of a Column Pagination Filter

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.20.3
    • Fix Version/s: 0.90.0
    • Component/s: Filters
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
       * A filter, based on the ColumnCountGetFilter, takes two arguments: limit and offset.
       * This filter can be used for row-based indexing, where references to other tables are stored across many columns, in order to efficient lookups and paginated results for end users.
      Show
       * A filter, based on the ColumnCountGetFilter, takes two arguments: limit and offset.  * This filter can be used for row-based indexing, where references to other tables are stored across many columns, in order to efficient lookups and paginated results for end users.
    • Tags:
      pagination, "row-based indexing", filter

      Description

      Client applications may need to do pagination, depending on the number of columns returned, it may be more efficient to perform pagination algorithms at the database level (similar to SQL's LIMIT and OFFSET). This will be an additional filter taking two parameters:

      • page
      • pageSize

      For every row, that gets returned, only a subset of columns are returned based on page and pageSize

      If the page / pageSize column goes over the limits, then no results are returned from the filter.

      A practical example for using a filter like this may be for folks doing Row-based indexing with Hbase.

        Attachments

          Activity

            People

            • Assignee:
              kida78 Paul Kist
              Reporter:
              kida78 Paul Kist
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 8h
                8h
                Remaining:
                Remaining Estimate - 8h
                8h
                Logged:
                Time Spent - Not Specified
                Not Specified