[ https://issues.apache.org/jira/browse/DRILL-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002662#comment-15002662 ]
Jacques Nadeau commented on DRILL-4070: --------------------------------------- Same question I asked Jason a minute ago. As I understand it, he hasn't been able to determine a way to distinguish between old Drill files and old non-Drill files. > Metadata Caching : min/max values are null for varchar columns in auto > partitioned data > --------------------------------------------------------------------------------------- > > Key: DRILL-4070 > URL: https://issues.apache.org/jira/browse/DRILL-4070 > Project: Apache Drill > Issue Type: Bug > Components: Metadata > Affects Versions: 1.3.0 > Reporter: Rahul Challapalli > Priority: Critical > Attachments: cache.txt, fewtypes_varcharpartition.tar.tgz > > > git.commit.id.abbrev=e78e286 > The metadata cache file created contains incorrect values for min/max fields > for varchar colums. The data is also partitioned on the varchar column > {code} > refresh table metadata fewtypes_varcharpartition; > {code} > As a result partition pruning is not happening. This was working after > DRILL-3937 has been fixed (d331330efd27dbb8922024c4a18c11e76a00016b) > I attached the data set and the cache file -- This message was sent by Atlassian JIRA (v6.3.4#6332)