Hi manish, after reviewing your PR, I do come across another idea of implementing this featureļ¼
I'd like to use an unique `FAKE` value to store the minmax for those columns. While judging the filter value with the fake minmax, we know that is a fake minmax, so the filter procedure just returns true. In this way, we do not need to modify the metadata and can reduce many code changes. BTW, It seems the we already use a unique value for 'NULL' during converting, so I think a unique value for fake minmax is acceptable. How do you think about it? -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
