Synapse Spark Pool - :setting -deprecation'

Question

question

data-walker asked Mar 29, '22 PRADEEPCHEEKATLA-MSFT commented Apr 25, '22

Synapse Spark Pool - :setting -deprecation'

I am getting this warning in the Notebook in Azure Synapse: warning: there were two deprecation warnings; for details, enable :setting -deprecation' or :replay -deprecation'

In the Notebook, how do I enable this to see what has been deprecated?

azure-synapse-analytics azure-databricks

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PRADEEPCHEEKATLA-MSFT · Mar 30 at 08:09 AM

Hello @data-walker,

We are reaching out to the internal team to get the more details on this ask. I will be update you once I hear back from the team.

0 ·

data-walker PRADEEPCHEEKATLA-MSFT · Mar 30 at 11:40 PM

It is something to do with the synapsesql function but the error wont tell me what is deprecated it just gives the warning

warning: there was one deprecation warning; for details, enable :setting -deprecation' or :replay -deprecation'

0 ·

PRADEEPCHEEKATLA-MSFT data-walker · Apr 05 at 02:54 AM

Hello @data-walker,

Internal team has confirmed this as an known issue. It will be fixed asap.

I will be update you once the hotfix has been deployed.

0 ·

Show more comments

PRADEEPCHEEKATLA-MSFT · Apr 22 at 03:43 AM

Hello @data-walker,

Following up to see if the below suggestion was helpful. And, if you have any further query do let us know.

Please don't forget to click on or upvote button whenever the information provided helps you.

0 ·

Answer 1 · 2022-04-20T06:46:43.923Z

PRADEEPCHEEKATLA-MSFT answered Apr 20, '22 PRADEEPCHEEKATLA-MSFT commented Apr 25, '22

Hello @data-walker,

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

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PRADEEPCHEEKATLA-MSFT · Apr 25 at 04:42 AM

Hello @data-walker,

Just checking in to see if the above answer helped. If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

0 ·

question