alamb opened a new issue, #6192: URL: https://github.com/apache/arrow-datafusion/issues/6192
### Describe the bug When I was debugging in IOx using logs, I got a lot of low level, per partition messages like the following: ``` 2023-05-01T19:55:32.453129Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 5 2023-05-01T19:55:32.453130Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 0 2023-05-01T19:55:32.453141Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 4 2023-05-01T19:55:32.453155Z DEBUG datafusion::physical_plan::projection: Start ProjectionExec::execute for partition 15 of context session_id 022a588e-54dc-4d9e-8131-bfee0b7cce75 and task_id None 2023-05-01T19:55:32.453164Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 13 2023-05-01T19:55:32.453167Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 15 2023-05-01T19:55:32.453169Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 11 2023-05-01T19:55:32.453179Z DEBUG datafusion::physical_plan::projection: Start ProjectionExec::execute for partition 1 of context session_id 022a588e-54dc-4d9e-8131-bfee0b7cce75 and task_id None 2023-05-01T19:55:32.453194Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 1 2023-05-01T19:55:32.453196Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 14 2023-05-01T19:55:32.453200Z DEBUG datafusion::physical_plan::projection: Start ProjectionExec::execute for partition 4 of context session_id 022a588e-54dc-4d9e-8131-bfee0b7cce75 and task_id None 2023-05-01T19:55:32.453203Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 15 2023-05-01T19:55:32.453207Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 9 2023-05-01T19:55:32.453212Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 4 2023-05-01T19:55:32.453228Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 14 2023-05-01T19:55:32.453233Z DEBUG datafusion::physical_plan::projection: Start ProjectionExec::execute for partition 11 of context session_id 022a588e-54dc-4d9e-8131-bfee0b7cce75 and task_id None 2023-05-01T19:55:32.453234Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 10 2023-05-01T19:55:32.453240Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 3 2023-05-01T19:55:32.453245Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 11 2023-05-01T19:55:32.453246Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 5 2023-05-01T19:55:32.453259Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 6 2023-05-01T19:55:32.453265Z DEBUG datafusion::physical_plan::repartition: Before returning stream in RepartitionExec::execute for partition: 8 2023-05-01T19:55:32.453289Z DEBUG datafusion::physical_plan::projection: Start ProjectionExec::execute for partition 9 of context session_id 022a588e-54dc-4d9e-8131-bfee0b7cce75 and task_id None 2023-05-01T19:55:32.453313Z DEBUG datafusion::physical_plan::projection: Start ProjectionExec::execute for partition 10 of context session_id 022a588e-54dc-4d9e-8131-bfee0b7cce75 and task_id None 2023-05-01T19:55:32.453317Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 9 2023-05-01T19:55:32.453350Z DEBUG datafusion::physical_plan::repartition: Start RepartitionExec::execute for partition: 10 ``` ### To Reproduce Turn on `RUST_LOG=debug` and run a query ### Expected behavior I would like less detail at debug level -- if I want this level of detail I would rather have it at trace level ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
