Where in the Spark UI can one diagnose a performance problem induced by not leveraging predicate push-down?
Select an option, then click Submit answer.
Reference / correct answer:
In the Query Detail screen, by interpreting the Physical Plan
Most accepted answer: C. In the Query Detail screen, by interpreting the Physical Plan
Community votes: C=3
Selected Answer: C suretly C upvoted 1 times
Selected Answer: C Option C is correct because you can diagnose performance issues related to predicate push-down by examining the Physical Plan in the Query Detail screen of the Spark UI. Predicate push-down is a feature where filtering conditions (predicates) are applied as early as possible, typically in the data scan operation, to reduce the amount of data being read. If predicate push-down is not happening, the physical plan will show that the filter operation is being applied after the data is read, leading to inefficient queries. upvoted 2 times
Selected Answer: C Look at the Physical Plan upvoted 1 times