[ 
https://issues.apache.org/jira/browse/DRILL-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109037#comment-15109037
 ] 

Victoria Markman commented on DRILL-4247:
-----------------------------------------

We would never see this warning, because it is printed in drillbit.out and not 
drillbit.log. It looks like it is coming from parquet library. The only way to 
find out if this is regression or not is to test it in previous release.

> Parquet statistics are ignored for tables created with partitioning
> -------------------------------------------------------------------
>
>                 Key: DRILL-4247
>                 URL: https://issues.apache.org/jira/browse/DRILL-4247
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Deneche A. Hakim
>            Assignee: Jason Altekruse
>
> I am running all queries in embedded mode, using the latest master:
> {noformat}
> * e4372f2 2015-12-17 | DRILL-4242: Updates to storage-mongo (HEAD -> master, 
> origin/master, origin/HEAD, origin/DRILL-3478) [Ross Lawley]
> {noformat}
> First run the following query:
> {noformat}
> create table dfs.tmp.test partition by (l_moddate) as select l.*, l_shipdate 
> - extract(day from l_shipdate) + 1 l_moddate from cp.`tpch/lineitem.parquet` 
> l;
> {noformat}
> then query the table just created:
> {noformat}
> select * from dfs.tmp.test order by l_orderkey;
> {noformat}
> after you close sqlline you should see the following warning
> {noformat}
> Jan 5, 2016 11:25:55 AM WARNING: org.apache.parquet.CorruptStatistics: 
> Ignoring statistics because created_by is null or empty! See PARQUET-251 and 
> PARQUET-297
> {noformat}
> To make sure the warning was not generated by the ctas, I closed sqlline 
> between the queries.
> I tried some variations of the query and I don't see the warning when there 
> is no partitioning or if I partition on a column other than date (didn't try 
> all types though).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to