sachouche 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_r201833441
##########
File path:
exec/java-exec/src/main/java/org/apache/drill/exec/util/record/RecordBatchStats.java
##########
@@ -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
statistics
+ final String statsLoggingOperator =
context.getOptions().getString(ExecConstants.STATS_LOGGING_BATCH_OPERATOR_OPTION).toUpperCase();
+ 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:
operator-id-1,operator-id-2,..
+ final String[] operators = statsLoggingOperator.split(",");
+ final String operatorId = oContext.getStats().getId().toUpperCase();
+
+ for (int idx = 0; idx < operators.length; idx++) {
+ // We use "contains" because the operator identifier is a composite
string; e.g., 3:[PARQUET_ROW_GROUP_SCAN]
+ if (operatorId.contains(operators[idx])) {
+ return true;
+ }
+ }
+
+ return false;
+ }
+ }
+
+ /**
+ * @see {@link RecordBatchStats#logRecordBatchStats(String, RecordBatch,
RecordBatchStatsContext)}
+ */
+ public static void logRecordBatchStats(RecordBatch recordBatch,
+ RecordBatchStatsContext batchStatsContext) {
+
+ logRecordBatchStats(null, recordBatch, batchStatsContext);
+ }
+
+ /**
+ * Logs record batch statistics for the input record batch (logging happens
only
+ * when record statistics logging is enabled).
+ *
+ * @param sourceId optional source identifier for scanners
+ * @param recordBatch a set of records
+ * @param batchStatsContext batch stats context object
+ */
+ public static void logRecordBatchStats(String sourceId,
Review comment:
@bitblender, this utility can always be enhanced to cater to more use-cases.
The use case you just alluded to can be handled by the default
enabled_operators settings where all operators will by default output a
minimalistic summary for their output batch.
----------------------------------------------------------------
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:
[email protected]
With regards,
Apache Git Services
