Closed liurenjie1024 closed 1 day ago
with https://github.com/NVIDIA/spark-rapids/pull/10999, we can start to ues LORE at customer site for simple cases like GpuAggregateExec. I can think of these remaining issues to address:
The list might be incomplete.
target Exec must be GpuExec, target Exec must have a child and it must be GpuExec
I think we only need to care about GpuExec
?
Is your feature request related to a problem? Please describe. We want to implement a lore framework to support all operators.
Describe the solution you'd like We need to figure out a way to allow user to tell us the operator id at runtime, e.g. we call it
lore_id
. Thelore_id
should be determinstic when given same spark configration, spark sql, and input data. Then in the second run we will dump the operators' input data, meta data(e.g. plan information) so that we can replay it in local. Ideally, we will also dump nsight tracing utilizing work here: https://github.com/NVIDIA/spark-rapids/pull/10870Describe alternatives you've considered No.
Additional context No.