Github user jkbradley commented on the issue:

    https://github.com/apache/spark/pull/14547
  
    I'd recommend overriding setImpurity in the relevant concrete classes.  In 
those, you can add warnings in the Scala doc and also add logWarning messages 
about deprecation.  That's almost as good as deprecation annotations.


---
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