[
https://issues.apache.org/jira/browse/DRILL-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807496#comment-13807496
]
Jacques Nadeau commented on DRILL-266:
--------------------------------------
Here is an outline of basic usage. Feel free to share your thoughts. You can
point the tool at an hdfs format path and provide a query id. The tool then
outputs key statistics about the data generated. There are two main modes:
statistics mode and data dump mode.
<<Query Mode>>
$drill-dumpcat
--file=local:///tmp/drilltrace/[queryid]_[tag]_[majorid]_[minor]_[operator]
Drill Trace Dump Diagnostics output:
Batches: 135
Records: 53,214
Average Record Size: 74 bytes
Total Data Size: 12,345 bytes
Number of Empty Batches: 1
Schema changes: 1
Schema change batch indices: 0
<<Batch Mode>>
$drill-dumpcat
--file=local:///tmp/drilltrace/[queryid]_[tag]_[majorid]_[minor]_[operator]
--batch=123 --include-headers=true
Records: 1
Average Record Size: 8 bytes
Total Data Size: 8 bytes
Schema Information
name: col1, minor_type: int4, data_mode: nullable
name: col2, minor_type: int4, data_mode: non-nullable
col1 col2
1 35
> Build tools to interpret the output dumped by the diagnostic operator
> ---------------------------------------------------------------------
>
> Key: DRILL-266
> URL: https://issues.apache.org/jira/browse/DRILL-266
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Mehant Baid
> Assignee: Jinfeng Ni
>
> DRILL-256 (https://issues.apache.org/jira/browse/DRILL-256) encompasses two
> parts
> 1. Implement the diagnostic operator which dumps data to log files
> 2. Build tools to interpret the the output dumped by the diagnostic operator.
> This bug should address part 2. We need to build tools to interpret the
> dumped bytes by the diagnostic operator and print it to screen in a nice
> format.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
