[arrow-datafusion] branch master updated: I think using info in formal code is better than using println. (#2020)

[alamb]

This is an automated email from the ASF dual-hosted git repository.

alamb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git


The following commit(s) were added to refs/heads/master by this push:
     new 7ed3be6  I think using info in formal code is better than using 
println. (#2020)
7ed3be6 is described below

commit 7ed3be6642651284708659fb7a0eee6f082baec2
Author: fire <32766901+silence-cod...@users.noreply.github.com>
AuthorDate: Sun Mar 20 18:23:02 2022 +0800

    I think using info in formal code is better than using println. (#2020)
    
    Co-authored-by: p00512853 <pankangt...@huawei.com>
---
 datafusion/src/physical_plan/file_format/parquet.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/datafusion/src/physical_plan/file_format/parquet.rs 
b/datafusion/src/physical_plan/file_format/parquet.rs
index f532f6a..9731efb 100644
--- a/datafusion/src/physical_plan/file_format/parquet.rs
+++ b/datafusion/src/physical_plan/file_format/parquet.rs
@@ -50,7 +50,7 @@ use arrow::{
     error::{ArrowError, Result as ArrowResult},
     record_batch::RecordBatch,
 };
-use log::debug;
+use log::{debug, info};
 use parquet::arrow::ArrowWriter;
 use parquet::file::{
     metadata::RowGroupMetaData,
@@ -249,7 +249,7 @@ impl ExecutionPlan for ParquetExec {
                 limit,
                 partition_col_proj,
             ) {
-                println!(
+                info!(
                     "Parquet reader thread terminated due to error: {:?} for 
files: {:?}",
                     e, partition
                 );