-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: delete records #4980
feat: delete records #4980
Conversation
for more information, see https://pre-commit.ci
Co-authored-by: David Berenstein <[email protected]>
Co-authored-by: David Berenstein <[email protected]>
@sdiazlor there is a merge conflict. Can you try to resolve it please :) ? |
```python | ||
status_filter = rg.Query( | ||
filter = rg.Filter(("status", "==", "pending")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I'm seeing this and after the discussion this morning about task distribution. Does it make sense if we rename the current status to something like "response.status"? (not to handle on this PR, just a question)
cc @burtenshaw @davidberenstein1957 @dvsrepo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I missed the task distribution meeting but what is the reasoning behind the raneme to the "response.status"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point, we'll introduce status at a record-level. So having a general status
name can create some confusion later.
Description
Basic method to delete the records. Records are still ingested to be validated, but I don't think we need to allow data structures in this workflow.
Closes #4930
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)
How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference
tests
)Checklist
CHANGELOG.md
file (See https://keepachangelog.com/)