Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-14034

Calcite integration. IndexCondition refactoring

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.15
    • sql

    Description

      Currently IndexCondition is quite cumbersome and hard to understand. The difference between bounds and conditions is unclear as well as unclear what should be used to estimate a selectivity and what should be used to estimate a self cost.

      Thus I suggest to change it in a follow way:

      • remove [lower|upper]Cond
      • bounds remains as is
      • self cost estimation of an AbstractIndex should be calculated with regard to bounds
      • selectivity should be calculated with regards to whole condition that is member of ProjectableFilterableTableScan

      Attachments

        Issue Links

          Activity

            People

              alex_pl Aleksey Plekhanov
              korlov Konstantin Orlov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: