You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/CrestApps.Core.Docs/docs/changelog/v1.0.0.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,3 +72,5 @@ description: Initial standalone release notes for the CrestApps.Core repository.
72
72
- distinguishes uploaded vision images from searchable documents in the shared document-availability prompt so multimodal chat sessions analyze supported attached images directly instead of defaulting to document-tool or metadata-only responses
73
73
- caps the total uploaded vision-image bytes loaded into a single multimodal request through `ChatDocumentsOptions.MaxVisionInputBytesPerRequest`, removes the extra `MemoryStream` copy when attaching those images, and documents how to resolve a vision-capable chat client for direct image-description requests
74
74
- adds `CrestApps.Core.PostgreSQL` and `CrestApps.Core.AI.PostgreSQL` packages providing a lightweight PostgreSQL + pgvector vector search backend as an alternative to Elasticsearch and Azure AI Search, registers the same keyed services (`ISearchIndexManager`, `ISearchDocumentManager`, `IDataSourceContentManager`, `IDataSourceDocumentReader`, `IODataFilterTranslator`) under the `"PostgreSQL"` provider name, supports `AddAIDocuments()`, `AddAIDataSources()`, and `AddAIMemory()` builder extensions, and integrates into both MVC and Blazor sample hosts
75
+
- fixes hosted document and data-source indexing flows so background workers create a scoped service provider before resolving scoped indexing services, preventing upload-triggered failures and similar nightly alignment lifetime issues
76
+
- standardizes Azure AI Search configuration on top-level `AuthenticationType`, `ApiKey`, `IdentityClientId`, and `IndexPrefix` settings under `CrestApps:AzureAISearch`, and refreshes the sample host / docs examples to list the full supported option set in one place
|`ApiKey`|`string`| No | — | Admin API key. When empty, `DefaultAzureCredential` is used for authentication. |
204
+
|`AuthenticationType`|`string`| No |`Default`| Supported values: `Default`, `ApiKey`, `ManagedIdentity`. |
205
+
|`ApiKey`|`string`| No | — | Admin API key. Required when `AuthenticationType` is `ApiKey`. |
206
+
|`IdentityClientId`|`string`| No | — | Optional managed identity client ID used by `DefaultAzureCredential` or `ManagedIdentityCredential`. |
207
+
|`IndexPrefix`|`string`| No | — | Optional prefix applied to framework-managed index names. |
172
208
173
209
:::info
174
210
When `Endpoint` is provided, the framework registers a `SearchIndexClient` singleton that all keyed services share. If `Endpoint` is empty or null, no client is registered and the data source is effectively disabled.
A successful response returns a JSON list of indexes (possibly empty).
189
225
226
+
:::info
227
+
The framework writes embeddings into the `embedding` vector field for AI Documents, AI Memory, and AI Data Sources. In Azure Search Explorer, make sure the vector field is retrievable and clear **Hide vector values in search results** if you want the raw float array to appear in the portal response.
228
+
:::
229
+
190
230
### 2. Verify from the Application
191
231
192
232
Inject `ISearchIndexManager` (keyed by `"AzureAISearch"`) and check if the connection is live:
return$"Unable to validate whether the remote index '{profile.IndexFullName}' already exists because the remote search provider rejected the configured credentials. Verify the endpoint and use credentials with index management permissions.";
150
+
}
151
+
152
+
return$"Unable to validate whether the remote index '{profile.IndexFullName}' already exists.";
0 commit comments