[GH-ISSUE #62] API methods to check processing status #63

New issue

Closed

opened 2026-02-27 15:54:47 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:54:47 +03:00

Owner

Originally created by @jenkin on GitHub (Aug 9, 2017).
Original GitHub issue: https://github.com/RD17/ambar/issues/62

Sending file to ambar is an asynchronous task, so you have to poll API with the file id to check if processing is finished and to retrieve parsed text. But I find the endpoint response is "404 file not found" both for in processing files and failed ones.

Can you add a persistent status endpoint with similar information I can see in rabbit log?

Originally created by @jenkin on GitHub (Aug 9, 2017). Original GitHub issue: https://github.com/RD17/ambar/issues/62 Sending file to ambar is an asynchronous task, so you have to poll API with the file id to check if processing is finished and to retrieve parsed text. But I find the endpoint response is "404 file not found" both for in processing files and failed ones. Can you add a persistent status endpoint with similar information I can see in rabbit log?

kerem

2026-02-27 15:54:47 +03:00

closed this issue
added the
enhancement

wontfix
labels

kerem commented

2026-02-27 15:54:47 +03:00

Author

Owner

@sochix commented on GitHub (Aug 9, 2017):

@jenkin thank you for your feedback! We'll add this to our internal roadmap

@sochix commented on GitHub (Aug 9, 2017): @jenkin thank you for your feedback! We'll add this to our internal roadmap

kerem commented

2026-02-27 15:54:47 +03:00

Author

Owner

@jenkin commented on GitHub (Aug 9, 2017):

Thank you very much, for now I'll use a cache to keep track of processing files and set a time interval to check failed ones.

@jenkin commented on GitHub (Aug 9, 2017): Thank you very much, for now I'll use a cache to keep track of processing files and set a time interval to check failed ones.

kerem commented

2026-02-27 15:54:47 +03:00

Author

Owner

@stale[bot] commented on GitHub (Sep 10, 2018):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 10, 2018): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kerem referenced this issue

2026-02-27 15:55:19 +03:00

[GH-ISSUE #149] ERROR: for serviceapi Container "xxxx" is unhealthy. #150

kerem referenced this issue

2026-02-27 15:55:33 +03:00

[GH-ISSUE #193] Downloading a file from Ambar Search & view files from mounting location (Crawler) #189