fix: fix import error on using the cognitive services on AML spark clusters

[mhamilton723]

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Briefly describe the changes included in this Pull Request.

How is this patch tested?

• I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

• No. You can skip this section.
• Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

• No. You can skip this section.
• Yes. Make sure you have added samples following below steps.

1. Find the corresponding markdown file for your new feature in website/docs/documentation folder.
   Make sure you choose the correct class estimators/transformers and namespace.
2. Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
3. Make sure the DocTable points to correct API link.
4. Navigate to website folder, and run yarn run start to make sure the website renders correctly.
5. Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
6. Make sure the WebsiteSamplesTests job pass in the pipeline.

[github-actions]

Hey @mhamilton723 👋!
Thank you so much for contributing to our repository 🙌.
Someone from SynapseML Team will be reviewing this pull request soon.

We use semantic commit messages to streamline the release process.
Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix.
This helps us to create release messages and credit you for your hard work!

Examples of commit messages with semantic prefixes:

• fix: Fix LightGBM crashes with empty partitions
• feat: Make HTTP on Spark back-offs configurable
• docs: Update Spark Serving usage
• build: Add codecov support
• perf: improve LightGBM memory usage
• refactor: make python code generation rely on classes
• style: Remove nulls from CNTKModel
• test: Add test coverage for CNTKModel

To test your commit locally, please follow our guild on building from source.
Check out the developer guide for additional guidance on testing your change.

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov-commenter]

Codecov Report

Merging #1951 (08aac33) into master (fbb0d0a) will increase coverage by 0.86%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1951      +/-   ##
==========================================
+ Coverage   86.11%   86.98%   +0.86%     
==========================================
  Files         305      305              
  Lines       15993    15993              
  Branches      839      839              
==========================================
+ Hits        13772    13911     +139     
+ Misses       2221     2082     -139     

Impacted Files	Coverage Δ
...re/synapse/ml/cognitive/CognitiveServiceBase.scala	81.62% <ø> (+0.54%)	⬆️

... and 14 files with indirect coverage changes

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[github-actions]

Summary by GPT-4

The code change adds a try-except block around the import statement and the following lines that use the imported module. This is done to handle the ModuleNotFoundError exception that might be raised if the module is not found. If the exception is raised, it will be caught and passed, allowing the program to continue running without any issues.

Here's a summary of what has been changed:

1. Added a try-except block around the import statement for synapse.ml.mlflow.
2. If ModuleNotFoundError is raised, it will be caught and passed.
3. The rest of the code remains unchanged.

This change ensures that if the module is not found, it won't cause any issues in the program execution, and it will continue running without any problems.

Suggestions

No suggestions are needed as the changes in this PR seem to be appropriate and well-implemented.