Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Once a mapper in the MR index job succeeds, it should not need to be re-done in the event of the failure of one of the other mappers. The initial population of an index is based on a snapshot in time, so new rows getting after the index build has started and/or failed do not impact it.

      Also, there's a 1:1 correspondence between index rows and table rows, so there's really no need to dedup. However, the index rows will have a different row key than the data table, so I'm not sure how the HFiles are split. Will they potentially overlap and is this an issue?

        Attachments

        1. PHOENIX-2154-_HBase_Frontdoor_API_v2.patch
          40 kB
          Ravi Kishore Valeti
        2. PHOENIX-2154-_HBase_Frontdoor_API_v1.patch
          35 kB
          Ravi Kishore Valeti
        3. PHOENIX-2154-_HBase_Frontdoor_API_WIP.patch
          26 kB
          Ravi Kishore Valeti
        4. PHOENIX-2154-WIP.patch
          20 kB
          ravi
        5. IndexTool.java
          13 kB
          James Taylor

          Activity

            People

            • Assignee:
              rvaleti Ravi Kishore Valeti
              Reporter:
              jamestaylor James Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: