Keep Wiki data out of runtime images and clarify search semantics - #93
Open
areshand wants to merge 1 commit into
Open
Keep Wiki data out of runtime images and clarify search semantics#93areshand wants to merge 1 commit into
areshand wants to merge 1 commit into
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.
Why
The runtime build context currently copies the checked-in repository catalog into every agent image. The production trace also treated lexical search/name frequency as repository usage, which the Wiki cannot support.
What changes
wiki-service/catalogfrom the runtime image build context while retaining the provider-neutralwiki-queryclient.scoreMeaning: "lexical-relevance-only"andsupportsAggregation: false.Validation
Deployment
Source-only PR. It does not alter the S3 Wiki corpus, sync data, or deploy a service.