Skip to content

Conversation

@pjohari-ms
Copy link
Member

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

Copilot AI review requested due to automatic review settings November 5, 2025 19:57
@azure-client-tools-bot-prd
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the Azure CosmosDB Management SDK to API version 2025-10-15 and adds support for several new features including full-text indexing, vector index enhancements, priority-based execution, and additional restore parameters.

Key Changes

  • Updated API version from 2024-11-15 to 2025-10-15 across all operations
  • Added full-text indexing support with new FullTextPolicy, FullTextPath, and FullTextIndexPath models
  • Enhanced vector indexing with quantization and DiskANN index configuration options
  • Added priority-based execution feature with EnablePriorityBasedExecution and DefaultPriorityLevel properties
  • Added Float16 data type support for vector embeddings
  • Updated API specification paths to include /DocumentDB/ segment

Reviewed Changes

Copilot reviewed 1 out of 56 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
README.md Updated commit reference, API version to 2025-10-15, and API spec paths with /DocumentDB/ segment
Multiple Operations files Updated apiVersion string literals from "2024-11-15" to "2025-10-15" in all operation methods
VectorIndex.cs Added quantization parameters, indexing search list size, and shard key support
VectorEmbedding.cs Updated documentation to include Float16 data type
VectorDataType.cs Added Float16 constant
SqlContainerResource.cs Added FullTextPolicy property
SqlContainerGetPropertiesResource.cs Added FullTextPolicy property
RestorableSqlContainerPropertiesResourceContainer.cs Added FullTextPolicy property
IndexingPolicy.cs Added FullTextIndexes property
FullTextPolicy.cs New model for full-text indexing policy
FullTextPath.cs New model for full-text path configuration
FullTextIndexPath.cs New model for full-text index path
DefaultPriorityLevel.cs New enum for priority levels (High/Low)
DatabaseAccountUpdateProperties.cs Added priority-based execution properties
DatabaseAccountUpdateParameters.cs Added priority-based execution properties
DatabaseAccountGetResults.cs Added KeyVaultKeyUriVersion and priority-based execution properties
DatabaseAccountGetProperties.cs Added KeyVaultKeyUriVersion and priority-based execution properties
DatabaseAccountCreateUpdateProperties.cs Added priority-based execution properties
DatabaseAccountCreateUpdateParameters.cs Added priority-based execution properties
RestoreParameters.cs Added SourceBackupLocation property

``` yaml
commit: 2afa5b356adf6cf51209d2cf28d38644c69d9832
apiversion: "2024-11-15"
commit: main
Copy link

Copilot AI Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using 'main' as the commit reference is not recommended for production builds as it points to a moving target and can lead to non-reproducible builds. Consider using a specific commit SHA to ensure build reproducibility and version stability.

Copilot uses AI. Check for mistakes.
@isra-fel
Copy link
Member

isra-fel commented Nov 5, 2025

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@dolauli dolauli self-assigned this Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants