feat: activityRelations_data_copilot pipe#3463
Conversation
activityRelations_data_copilot pipe
borfast
left a comment
There was a problem hiding this comment.
I noticed you're getting the isContribution column but I don't know how or if is being used by whoever consumes this pipe. We're going to be removing this column soon, so if it's being used, we need to have a plan for how to change this.
Also, the entire tinybird-ci.yml file is commented out but there's no mention of that in the PR description, so I'm wondering if this was by mistake.
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
…com:CrowdDotDev/crowd.dev into feature/activityRelations-data-copilot-pipe
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
Changes proposed ✍️
Adds a new
activityRelations_data_copilotpipe for data copilot.It gets its data from
activityRelations_deduplicated_cleaned_ds. The only difference from the raw data source is that fields that contain PII (usernameandobjectMemberUsername) are omitted from the result set. Agents will use this pipe instead of the raw data source when they need raw data.Checklist ✅
Feature,Improvement, orBug.