Add Sample code to create a spark job with the azure synapse-spark client library.

[ouphi]

Add Sample code showing how to submit a spark job to an existing pool, with the azure synapse-spark client library. This example works with a pyspark script stored in Azure Blob File System.

[opbld32]

Learn Build status updates of commit c9575bf:

:warning: Validation status: warnings

File	Status	Preview URL	Details
docs-ref-services/preview/synapse-spark-readme.md	:warning:Warning	View (azure-node-preview)	Details

docs-ref-services/preview/synapse-spark-readme.md

• Line 0, Column 0: [Warning: h1-missing - See documentation] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
• Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
• Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
• Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'synapseanalytics'.
• Line 89, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Impressions' is duplicated. Within an article, alt text must be unique.
• Line 109, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Impressions' is duplicated. Within an article, alt text must be unique.
• Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
• Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ramyar' is not a valid Microsoft alias.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel