fix: send rag_for_content for GitLab code_files RAG indexing#7
Merged
Conversation
Populate rag_for_content when fields.content.rag is enabled and omit raw content from ingest to avoid doubling the code_files payload size.
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
1 participant
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.
Summary
rag_for_contentoncode_fileswhenfields.content.ragis enabled (control plane indexesrag_for_<field>per schema).contentfrom ingest when RAG is on to avoid doubling payload size (fixes HTTP 413 on large corpora).schema.ymldescription and add unit test for the RAG payload shape.Test plan
go test ./internal/probe/entities/...gitlab-probeand confirmcode_filesingest succeedsrag_for_contentand CP RAG reindex produces chunks