Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue link
https://issues.ravendb.net/issue/RDBC-1168
Description
AI connection strings can now use the native Anthropic (Claude) provider through
AnthropicSettings.Port of PR #23802
AnthropicSettings(apiKey, model, endpoint, maxOutputTokens, reasoningEffort, enablePromptCache, apiVersion),AiConnectionString.anthropicSettings,"Anthropic"inAiConnectorType,enablePromptCacheinIAiSettings.AiConnectionString.validate()rejects Anthropic with theTextEmbeddingsmodel type.DefaultMaxOutputTokensandDefaultApiVersionconstants (the server applies them), and theIAiSettingsmember onOllamaSettings(the Node.jsOllamaSettingsdoes not implementIAiSettings).test/Documents/Operations/AI/AnthropicSettingsTest.tsfor validation, endpoint resolution, compare and the connection string. The C# tests run against live LLM providers or test server internals and are not ported.npm run prepare,lint,check-exports,check-importsand the new unit tests pass locally. No server tests were run locally.Type of change
Target branch and backports
v7.2,v7.1,v7.0,v6.0)How risky is the change?
Backward compatibility
Server compatibility
Affected runtimes
Public API
src/index.ts(npm run check-exportspasses).package.jsonandCLIENT_VERSIONinsrc/Http/RequestExecutor.ts(sync / release PRs only)Documentation update
README.mdhas been updatedTesting by Contributor
npm run lint,npm run build,npm run check-exportsandnpm run check-importspass locallyRAVENDB_TEST_SERVER_PATH/RAVENDB_SERVER_VERSION)Dependencies
Is there any existing behavior change of other features due to this change?
Ticket: RDBC-1168
C# change: ravendb/ravendb#23802
SDK Sync Agent