Hello @Blair ,
Thanks for the question and using MS Q&A platform.
A deprecation warning message is returned when any end user exposed signatures are annotated with @deprecate warnings. Setting for a deprecation warning does not affect functionality of the interface/method itself. It’s a cautionary message. We retained it to avoid any fall-out after the major write path updates.
Note: The connector version released on 4/4 fixed this issue. If you have created the Spark Pool with Spark version 3.1 after 4/4, you shouldn’t see the warning message.
Hope this will help. Please let us know if any further queries.
- Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
- Want a reminder to come back and check responses? Here is how to subscribe to a notification
- If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators