-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Configured main index search field names in environment variables #1198
Merged
Conversation
This file contains 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
Coverage Report •
|
adamdougal
approved these changes
Aug 2, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
🎉 This PR is included in version 1.9.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
tylorbunting
pushed a commit
to Cognitive-Automation-Labs/chat-with-your-data-solution-accelerator
that referenced
this pull request
Nov 1, 2024
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.
Purpose
Configured main index search field names in environment variables to save the user needing to modify code?
Does this introduce a breaking change?
How to Test
Change the value of index search field names whatever you want to keep in environment variables from .env file or using azd env set command from VS code powershell terminal. Below are the env variables that has been added for index search field names:
AZURE_SEARCH_FIELDS_ID
AZURE_SEARCH_CONTENT_COLUMN
AZURE_SEARCH_CONTENT_VECTOR_COLUMN
AZURE_SEARCH_TITLE_COLUMN
AZURE_SEARCH_FIELDS_METADATA
AZURE_SEARCH_SOURCE_COLUMN
AZURE_SEARCH_CHUNK_COLUMN
AZURE_SEARCH_OFFSET_COLUMN
After changing/setting the values of above environment variables, run the below commands from VS code powershell terminal:
--azd auth login
--azd up
After successful deployment, delete the existing search index from search service and all the files from storage account container. And then upload the all the files again from admin screen.
What to Check
Once you uploaded all the files and got processed, verify that the search index got created with the updated values of index search field names that you have set in environment variables.
Please find below screenshot for your reference: