Details

    • Sub-task
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • None
    • 1.0.1
    • reader-core
    • None
    • 2

    Description

      In HoodieFileIndex, we have 5 indices support: 

       

      • RecordLevelIndexSupport
      • BucketIndexSupport
      • SecondaryIndexSupport
      • FunctionalIndexSupport
      • BloomFiltersIndexSupport
      • ColumnStatsIndexSupport

       
      But the logic would return early when the first index support applied and got pruned files.
      A better way is we can chain the multiple indices support all-together: one index support can still be applied based on the pruned files returned by another index support.

      Key points in contribution:
      1. think through the shared contract/param among these indices support;
      2. add a orthoganal test for random index supoprt composition, valid the result set and the indices support are applied effectively.
       

      Attachments

        Activity

          People

            danny0405 Danny Chen
            danny0405 Danny Chen
            Danny Chen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: