Vertica not picking the right projection
I have a table with 40 columns and and a super projection.
Actually i need only 2 columns for most of myqueries, so I created a query specific projection unsegmented on all nodes(refresed the table)
When I did an explain plan on the two columns from the table, I see the super projection in the plan,
I tried with SET_OPTIMIZER_DIRECTIVES('AvoidUsingProjections=') and avoided super projection and able to see the newly created projection ,
but when I do a select * from that table it throw me exception(not enough projections).
How to optionally overide the super projection?
What is the reason for such behaviour, i know vertica is able to pick the projection with minimum number of columns with which it could answer the query. but why is it unable to pick the right projection in this scenario...