DruidQuery could be affected by the presence of those columns - as they may interfere with the prefix selection
DruidCorrelateUnnestRule removes a project fully while it operates - which may cause all underlying columns to appear
Introduction of DruidRelFieldTrimmer which could remove unused columns under Correlate cause lots of _ differences between the decoupled and the old planner as DruidCorrelateUnnestRule essentially undoes the trimming
TestDataBuilder
definesd1
/d2
columnsDruidQuery
could be affected by the presence of those columns - as they may interfere with the prefix selectionDruidCorrelateUnnestRule
removes a project fully while it operates - which may cause all underlying columns to appearIntroduction of
DruidRelFieldTrimmer
which could remove unused columns underCorrelate
cause lots of_
differences between the decoupled and the old planner asDruidCorrelateUnnestRule
essentially undoes the trimming