Skip to content

Need new API endpoint to fetch the status of indexing #818

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

Closed
chuang-CE opened this issue May 14, 2025 · 8 comments
Closed

Need new API endpoint to fetch the status of indexing #818

chuang-CE opened this issue May 14, 2025 · 8 comments
Assignees

Comments

@chuang-CE
Copy link
Collaborator

We need an API endpoint that will let us know if there are still envelopes in process of being indexed. This way we don't queue up duplicate jobs.

@chuang-CE chuang-CE changed the title Need new API endpoint to fetch the status of sidekiq Need new API endpoint to fetch the status of indexing May 20, 2025
excelsior added a commit that referenced this issue May 20, 2025
@excelsior
Copy link
Collaborator

@chuang-CE The new API is available on sandbox:

GET /envelopes/:envelope_id/indexing_status

It shows whether an indexing job for the envelope is in the queue or not. And if it is, whether it's being processed right now or waiting for its turn.

excelsior added a commit that referenced this issue May 21, 2025
@excelsior
Copy link
Collaborator

@chuang-CE The new endpoint is this:

https://sandbox.credentialengineregistry.org/swagger/index.html#/Indexer/getApiIndexerStatsByCommunity

It returns the number of jobs waiting in the queue and the number of jobs being currently processed.

@chuang-CE
Copy link
Collaborator Author

@excelsior The new endpoint looks good, I can close this issue once that is merged and pushed to CLLC registry

@jeannekitchens
Copy link

@excelsior provide a timeline to get this merged/pushed.

@khasan786
Copy link
Collaborator

@excelsior Can you please provide a timeline for this change to be merged/ pushed in the CLLC Registry so we can close out this issue.

@excelsior
Copy link
Collaborator

Merged and pushed in the CLLC repo.

@edgarf
Copy link
Collaborator

edgarf commented May 27, 2025

@chuang-CE - should we close this issue?

@khasan786
Copy link
Collaborator

@chuang-CE Can we now go ahead and close this issue based on the update from edgarf above?. Please let me know and I can do it on your behalf.

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

No branches or pull requests

6 participants