Skip to content

refactor: remove extraction status_field from node type registry#1159

Merged
pyramation merged 1 commit into
mainfrom
feat/remove-extraction-status
May 14, 2026
Merged

refactor: remove extraction status_field from node type registry#1159
pyramation merged 1 commit into
mainfrom
feat/remove-extraction-status

Conversation

@pyramation
Copy link
Copy Markdown
Contributor

@pyramation pyramation commented May 14, 2026

Summary

Removes the status_field parameter from the extraction config in DataFileEmbedding and DataImageEmbedding node type definitions. Extraction lifecycle is tracked via _updated_at timestamps and job queue status, making a separate status column redundant.

Removed from both data-file-embedding.ts and data-image-embedding.ts:

  • extraction.properties.status_field parameter definition (was default: 'extraction_status')

Review & Testing Checklist for Human

Risk: green — TypeScript-only change, removes a parameter the SQL generator no longer reads.

  • Confirm no existing blueprints use extraction.status_field

Notes

Link to Devin session: https://app.devin.ai/sessions/2b5a29d83d3f478e8d3d972653b4879c
Requested by: @pyramation

Removes the status_field parameter from DataFileEmbedding and
DataImageEmbedding extraction config. Extraction lifecycle is now
tracked via _updated_at timestamps, not a separate status column.
@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@pyramation pyramation merged commit 86a09ea into main May 14, 2026
37 checks passed
@pyramation pyramation deleted the feat/remove-extraction-status branch May 14, 2026 07:01
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.

1 participant