ASF GitHub Bot commented on DRILL-6560:

bitblender commented on a change in pull request #1355: DRILL-6560: Enhanced 
the batch statistics logging enablement
URL: https://github.com/apache/drill/pull/1355#discussion_r201804507

 File path: 
 @@ -100,6 +108,119 @@ private String getQueryId(FragmentContext _context) {
       return "NA";
+    private boolean isBatchStatsEnabledForOperator(FragmentContext context, 
OperatorContext oContext) {
+      // The configuration can select what operators should log batch 
+      final String statsLoggingOperator = 
+      final String allOperatorsStr = "ALL";
+      // All operators are allowed to log batch statistics
+      if (allOperatorsStr.equals(statsLoggingOperator)) {
+        return true;
+      }
+      // No, only a select few are allowed; syntax: 
 Review comment:
   As a user setting *enabled_operators*, where do I find the format in which 
the name should be specified? For example, if Project has to be enabled, should 
the name be "Project", "Project_Record_Batch", or "ProjectRecordBatch" ? Where 
does one look to find the correct string?

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:

> Allow options for controlling the batch size per operator
> ---------------------------------------------------------
>                 Key: DRILL-6560
>                 URL: https://issues.apache.org/jira/browse/DRILL-6560
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Flow
>            Reporter: salim achouche
>            Assignee: salim achouche
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.14.0
> This Jira is for internal Drill DEV use; the following capabilities are 
> needed for automating the batch sizing functionality testing:
>  * Control the enablement of batch sizing statistics at session (per query) 
> and server level (all queries)
>  * Control the granularity of batch sizing statistics (summary or verbose)
>  * Control the set of operators that should log batch statistics

This message was sent by Atlassian JIRA

Reply via email to