[
https://issues.apache.org/jira/browse/DRILL-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986419#comment-14986419
]
ASF GitHub Bot commented on DRILL-3941:
---------------------------------------
Github user amansinha100 commented on a diff in the pull request:
https://github.com/apache/drill/pull/230#discussion_r43706195
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/store/parquet/Metadata.java
---
@@ -163,7 +163,9 @@ private ParquetTableMetadata_v1
getParquetTableMetadata(String path) throws IOEx
watch.start();
List<FileStatus> fileStatuses = getFileStatuses(fileStatus);
logger.info("Took {} ms to get file statuses",
watch.elapsed(TimeUnit.MILLISECONDS));
- return getParquetTableMetadata(fileStatuses);
+ ParquetTableMetadata_v1 metadata_v1 =
getParquetTableMetadata(fileStatuses);
+ logger.info("Took {} ms to read file metadata",
watch.elapsed(TimeUnit.MILLISECONDS));
--- End diff --
Is this time supposed to be only for reading file metadata ? This is
reporting the time inclusive of getFileStatuses().
> Add timing instrumentation around Partition Pruning
> ---------------------------------------------------
>
> Key: DRILL-3941
> URL: https://issues.apache.org/jira/browse/DRILL-3941
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Mehant Baid
> Assignee: Aman Sinha
>
> We seem to spending a chunk time doing partition pruning, it would be good to
> log timing information to indicate the amount of time we spend doing pruning.
> A little more granularity to indicate the time taken to build the filter tree
> and in the interpreter would also be good.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
