Thank you for posting query in Microsoft Q&A Platform.
I used same code which shared you. In my case, I am not seeing errors. Please check below screenshot.
Please check my Spark pool configurations.
Could you please cross verify your Spark Pool configurations with above and see if that helps?
Hope this helps. Please let us know if any further queries.
---------------
Please consider hitting Accept Answer
. Accepted answers helps community as well.
Hi @alexander tikhomirov ,
Yes. Looks strange behavior to me. I escalated this internally to see if any insights I can get. Will share updates once I here back. Thank you.
--------
Please consider hitting
Accept Answer
. Accepted answers helps community as well.The problem was with using print statement with multithreading.
answer from MS support
Issue:
You are having the below error:
• com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input at [Source: (String)''; line: 1, column: 0]
Cause:
Caused by python interpreter in Livy. For original python interpret, Livy uses "exec" to run code, and get output from redirected stderr and stdout. Then we would meet such issue(depends on which is finished first: pool shutdown and stdout flush).
For Ipython interpreter, we replace plain python interpreter with ipython, and all output are bounded to the corresponding statement, so ipython should help in this case.
So, this is caused by default Python Interpretor used and IPython interpreter should solve this issue.
Solution:
We are working to fix this issue, if everything goes as expected there is a new Azure Synapse deployment for Ipython start going to production after mid-February region by region, this should fix the issue when enabling the IPython feature.
Awesome. Thank you for sharing details here.
Hi @alexander tikhomirov ,
Could you please consider marking it as
accepted answer
? Accepted answers helps community as well. Thank you.Can you comment on the status of this fix? It says Mid-February the fix would start rolling out, however I have started seeing this error much more frequently in my own synapse workspace over the past month.
Sign in to comment