Skip to content

AISERVICES-1383 added async extraction background worker implementation - #1278

Open
manalilatkar wants to merge 1 commit into
IBM:mainfrom
manalilatkar:extract_async_endpoint
Open

AISERVICES-1383 added async extraction background worker implementation#1278
manalilatkar wants to merge 1 commit into
IBM:mainfrom
manalilatkar:extract_async_endpoint

Conversation

@manalilatkar

@manalilatkar manalilatkar commented Aug 18, 2026

Copy link
Copy Markdown
Member

In this PR:

  • async endpoint background task for extraction

Signed-off-by: Manali Latkar <manali.latkar@ibm.com>

@dharaneeshvrd dharaneeshvrd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see cleanup_staging_directory getting called at multiple occasions, why not call once via finally?

Otherwise overall lgtm since its same as the previous implementation.
Let's ensure to reuse the functionalities via a common method when you implement the batch processing.

# Fetch the job row so we know the schema_id and document name.
job_row = db_repo.get_job_by_id(job_id)
if job_row is None:
logger.error(f"Job {job_id} not found in DB at worker start; aborting.")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont you need to update the failure on db as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants