You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2020/02/29 01:33:07 UTC

[GitHub] [spark] zero323 commented on issue #27165: [SPARK-28264][PYTHON][SQL] Support type hints in pandas UDF and rename/move inconsistent pandas UDF types

zero323 commented on issue #27165: [SPARK-28264][PYTHON][SQL] Support type hints in pandas UDF and rename/move inconsistent pandas UDF types
URL: https://github.com/apache/spark/pull/27165#issuecomment-592805133
 
 
   Side note ‒ I've been working lately with mentee whose code depends heavily on `pandas_udf` wrappers for third party functions, i.e.
   
   ```python
   from foo import bar
   
   pandas_udf(bar, schema, type)
   ```
   
   one minor complain is that "will be deprecated" warnings tend to fill the log and notebook output (things are further complicated by the fact, that code is already annotated and reused, so injecting annotations is rather cumbersome).
   
   So I guess there are three questions:
   
   - Is the warning premature? Are plans to deprecate realistic, given current state of the ecosystem?
   - Is warning applicable for explicit wrap, instead of decorator?
   - Should we have more specific warning category than `UserWarning` that could be selectively suppressed?  Maybe something like `SparkDeprecationWarning` or `SparkPlannedDeprecationWarning`.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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