Fix missing segment ids in the conversation service #1084
Merged
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.
Changes proposed ✍️
What
🤖 Generated by Copilot at 2d0c86d
Added support for segmenting conversations by source in the data sink worker and the conversations library. This involved adding a
segmentId
parameter or filter to various methods and classes that deal with conversation data, and updating the database schema to store thesegmentId
of each conversation.
🤖 Generated by Copilot at 2d0c86d
Why
How
🤖 Generated by Copilot at 2d0c86d
segmentId
parameter toConversationService
methods to support segmenting conversations by source (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)ConversationRepository
methods to filter queries bysegmentId
and includesegmentId
column in insertions and updates (link, link, link, link, link, link, link, link, link, link, link, link, link)ConversationData
class to includesegmentId
column ininsertConversationColumnSet
value (link)Checklist ✅
Feature
,Improvement
, orBug
.