chore(closes OPEN-9405): allow specifying/logging question column name#607
Merged
viniciusdsmello merged 1 commit intomainfrom Mar 5, 2026
Merged
chore(closes OPEN-9405): allow specifying/logging question column name#607viniciusdsmello merged 1 commit intomainfrom
viniciusdsmello merged 1 commit intomainfrom
Conversation
viniciusdsmello
approved these changes
Mar 5, 2026
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.
Pull Request
Summary
This PR adds question support to the tracing system, mirroring the existing context handling for RAG use cases.
Users can now explicitly identify the user query field either via the
@trace(question_kwarg="my_param")decoratorparameter or by calling
log_question(value)manually inside a traced function.Internally, this introduces a
_rag_questioncontext variable, aget_rag_question()helper, and alog_question()public function; the question is included in the trace payload and the config is updated withquestion_column_name: "_question"automatically when set, eliminating the need for the backend to infer the question through heuristics.Changes
Context
OPEN-9405: Allow specifying/logging question column name
Testing