Uploaded image for project: 'Apache AsterixDB'
  1. Apache AsterixDB
  2. ASTERIXDB-2115

Component Id-based secondary to primary acceleration

    XMLWordPrintableJSON

    Details

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

      Description

      Previously, after we get a list of pkeys of secondary index, we perform point lookups against the primary index to fetch the records. When the number of disk components is large, we need to perform a lot of unnecessary searches because of false positives of bloom filters. However, since the memory components of all indexes are always flushed together, we can narrow down the candidate components of the primary index based on the component of the secondary index where the pkey is found.

      To enable this optimization, we first need to assign a unique Id to all components (including disk and memory), and guarantee all memory components of a dataset (partition) receive the same id upon creation. These component Ids are propagated to the primary index during query processing to facilitate primary index lookups.

        Attachments

          Activity

            People

            • Assignee:
              luochen01 Chen Luo
              Reporter:
              luochen01 Chen Luo
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: