Github user rdblue commented on the issue:

    https://github.com/apache/spark/pull/17540
  
    @zsxwing, what do you think the right way forward is? The "problem" with 
this patch seems to actually be a wide-spread problem with the data sources API 
-- it doesn't correctly link into SQL plans. I don't think this should be 
blocked by that problem since there are many queries that have no entry in the 
SQL tab (and also no metrics) and the current problems also cause the effects 
that @cloud-fan's test demonstrated where the write operation isn't shown.
    
    I think it would be better to introduce this patch, with regressions, and 
follow up by fixing the data source code.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to