Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-16973 Revisiting default value for hbase.client.scanner.caching
  3. HBASE-16987

Update javadoc, refguide, and unit tests so ""...setting [scan] cache is ... old style..."; instead limit by size and time.

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Scanners
    • None

    Description

      As yangzhe1991 says up in the parent issue, ""...Setting cache is an old style to limit size and time...". Lets make this indeed the case by updating javadoc, unit tests, and refguide in 1.3 going forward.

      Setting how many rows to get at a time when scanning was always less-than-satisfactory, unpredictable as the data a row could contain. The hard work done to get us up on a size/time basis should be underlined and evangelized as the new norm. Thats what this issue is about (see parent issue for the kinds of problems we run into when it caching is the awkward row-count basis).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              stack Michael Stack
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: