You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/08/05 10:42:51 UTC
[GitHub] [arrow-datafusion] thinkharderdev commented on issue #3033: Need to add an unique id to MetricsSet or ExecutionPlanMetricsSet
thinkharderdev commented on issue #3033:
URL: https://github.com/apache/arrow-datafusion/issues/3033#issuecomment-1206306535
> > A single session could have multiple statements run concurrently. And a statement_id is not enough to differ metrics either.
>
> That is a good point. I still think `statement_id` is likely necessary -- sounds like it would also be prudent to add a `execution_plan_id` or `operator_id` to `ExecutionPlan` or `LogicalPlan` as well to properly identify the execution? I can't remember if Ballista sends `dyn ExecutionPlans` or `LogicalPlans` to the executors.
On Ballista we send the `ExecutionPlan` and the `ShuffleWriteExec` should already have a `job_id` attached.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org