[Join Optimization] Eligibility for join optimization should not depend featureFlagCostBasedRanker

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we consult featureFlagCostBasedRanker as part of join eligibility checks. The team discussed that we the join flag implies CBR so we should avoid the intertwining of these flags (don't bail out of join is the CBR feature flag is disabled).

            Assignee:
            Unassigned
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: