Skip to content
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

Merged
merged 11 commits into from
Jun 13, 2024
Merged

feat: delete records #4980

merged 11 commits into from
Jun 13, 2024

Conversation

sdiazlor
Copy link
Contributor

@sdiazlor sdiazlor commented Jun 7, 2024

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)

  • New feature (non-breaking change which adds functionality)
  • Refactor (change restructuring the codebase without changing functionality)
  • Improvement (change adding some improvement to an existing functionality)

How Has This Been Tested

(Please describe the tests that you ran to verify your changes. And ideally, reference tests)

  • Test A
  • Test B

Checklist

  • I added relevant documentation
  • I followed the style guidelines of this project
  • I did a self-review of my code
  • I made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I filled out the contributor form (see text above)
  • I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@sdiazlor sdiazlor requested review from frascuchon and burtenshaw June 7, 2024 15:46
@sdiazlor sdiazlor linked an issue Jun 10, 2024 that may be closed by this pull request
@davidberenstein1957
Copy link
Member

@sdiazlor there is a merge conflict. Can you try to resolve it please :) ?

```python
status_filter = rg.Query(
filter = rg.Filter(("status", "==", "pending"))
Copy link
Member

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

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"?

@frascuchon

Copy link
Member

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.

@sdiazlor sdiazlor merged commit e7efb09 into feat/v2.0.0 Jun 13, 2024
24 of 26 checks passed
@sdiazlor sdiazlor deleted the feat/feat-delete-records branch June 13, 2024 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEAT] Delete records
4 participants