Related Issues/PRs

What changes are proposed in this pull request?

This PR adds support for retrieving datasets by name in non-Databricks (OSS) environments. Previously, get_dataset() in OSS only accepted dataset_id, while Databricks environments used name (UC table name). Now both parameters work in OSS.

Changes:

• Add _validate_non_databricks_get_params to validate that either name OR dataset_id is provided (not both, not neither)
• Add _resolve_dataset_by_name helper that uses search_datasets to find the dataset by name
  • Uses smart quoting (double quotes for names without ", single quotes for names without ')
  • Uses pattern matching for clean result handling
  • Raises appropriate errors for not found / multiple matches
• Update get_dataset to resolve name to dataset_id when name is provided
• Move MlflowClient, MlflowException, and error codes to top-level imports

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests

Added 7 new tests:

• test_get_dataset_by_name_oss - basic name lookup works
• test_get_dataset_by_name_not_found - raises when name doesn't exist
• test_get_dataset_by_name_multiple_matches - raises error on duplicate names
• test_get_dataset_both_name_and_id_error - rejects both params
• test_get_dataset_neither_name_nor_id_error - rejects neither
• test_get_dataset_name_with_single_quote - handles names with '
• test_get_dataset_name_with_double_quote - handles names with "

All 76 tests pass: uv run pytest tests/genai/datasets/test_fluent.py -v

Does this PR require documentation update?

• No. You can skip the rest of this section.

The docstring for get_dataset() has been updated to reflect the new behavior.

Release Notes

Is this a user-facing change?

• Yes. Give a description of this change to be included in the release notes for MLflow users.

get_dataset() now supports retrieving datasets by name in non-Databricks environments. Users can use either get_dataset(name="my_dataset") or get_dataset(dataset_id="d-xxx") to retrieve a dataset.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging

How should the PR be classified in the release notes? Choose one:

• rn/feature - A new user-facing feature worth mentioning in the release notes

Should this PR be included in the next patch release?

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)