[
https://issues.apache.org/jira/browse/DRILL-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806517#comment-13806517
]
Mehant Baid commented on DRILL-256:
-----------------------------------
For now you have to manually inject the trace operator in the physical plan
(for an example look at the unit test simple_trace.json). TraceInjector.java
traverses the set of operators and injects trace operator before every
operator. Since the trace operator does not work with hyper vectors yet,
TraceInjector is not invoked anywhere.
Yes, dumping the entire record batch data is a lot of writes, Steven suggested
that we write this to a distributed file system instead of local file system.
But I think having some sort of level with the trace operator is a good idea.
Based on the level associated with the trace operator we either only dump
metadata, record batch data or other statistics like Ben mentioned.
> Implement Diagnostic Operator
> -----------------------------
>
> Key: DRILL-256
> URL: https://issues.apache.org/jira/browse/DRILL-256
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Jacques Nadeau
> Assignee: Mehant Baid
> Attachments: Revision_1-DRILL-256.patch
>
>
> Support inserting a diagnostic physical operator into a physical plan that
> records the record batches output of a preceding operator. Additionally,
> provide a tool to view this data.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
