[
https://issues.apache.org/jira/browse/DRILL-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612201#comment-16612201
]
ASF GitHub Bot commented on DRILL-6724:
---------------------------------------
KazydubB commented on a change in pull request #1455: DRILL-6724: Convert
IndexOutOfBounds exception to UserException with …
URL: https://github.com/apache/drill/pull/1455#discussion_r217050673
##########
File path:
contrib/storage-kafka/src/main/java/org/apache/drill/exec/store/kafka/KafkaRecordReader.java
##########
@@ -116,6 +118,7 @@ public int next() {
if (++messageCount >= DEFAULT_MESSAGES_PER_BATCH) {
break;
}
+ currentMessageCount = messageCount;
Review comment:
Good point, removed local variable.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Dump operator context to logs when error occurs during query execution
> ----------------------------------------------------------------------
>
> Key: DRILL-6724
> URL: https://issues.apache.org/jira/browse/DRILL-6724
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.14.0
> Reporter: Bohdan Kazydub
> Assignee: Bohdan Kazydub
> Priority: Major
> Fix For: 1.15.0
>
>
> Sometimes when an error occurs it may be helpful to have operator stack with
> context data along with original stacktrace to help developers to track down
> a failure. To achieve this, each operator should provide a context which can
> be dumped to logs. In the end of FragmentExecutor's execution if the state is
> FAILED the operator stack will be dumped to logs before exception stacktrace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
