Azure / Azure/azure-sdk-for-python
Batch analysis result not retrievable
- Vorherrschende Sprache
- Python
- Sterne
- 5.6k
- Forks
- 3.4k
- Ø Merge
- 2 T. 2 Std.
- Gemergte PRs (30 T.)
- 202
Beschreibung
- **Package Name**: azure-ai-documentintelligence
- **Package Version**: 1.0.2
- **Operating System**: Windows 10
- **Python Version**: 3.13.11
**Describe the bug**
I tried following the sample tutorials [sample_analyze_batch_documents.py](https://github.com/Azure/azure-sdk-for-python/blob/d47bfafcc4f72d08911f87f0ab34b57f5cdc72f4/sdk/documentintelligence/azure-ai-documentintelligence/samples/sample_analyze_batch_documents.py#L48) and [sample_analyze_batch_documents_async.py](https://github.com/Azure/azure-sdk-for-python/blob/d47bfafcc4f72d08911f87f0ab34b57f5cdc72f4/sdk/documentintelligence/azure-ai-documentintelligence/samples/async_samples/sample_analyze_batch_documents_async.py#L49), and in both cases, the mechanism to verify whether the operation is concluded does not work.
Specifically, I always get the message "The batch analyze is still in process..." even when I know for a fact that the analysis has concluded.
I also tried implementing a solution by using the method [add_done_callback](https://learn.microsoft.com/en-us/python/api/azure-core/azure.core.polling.lropoller?view=azure-python#azure-core-polling-lropoller-add-done-callback) but this also does not work. Unfortunately, there is no sample that illustrates the correct use of this method to monitor a batch analysis.
**To Reproduce**
Steps to reproduce the behavior:
1. run the samples.
**Expected behavior**
The prints should reflect the status of the batch analysis operation.
Beitragsleitfaden
Rechercherichtung
Start by running sample_analyze_batch_documents.py and async_samples/sample_analyze_batch_documents_async.py in the azure-ai-documentintelligence package, focusing on how completion status is checked. Read the LROPoller add_done_callback entry point mentioned in the report and compare its behavior with the samples. Done means the samples and callback path accurately reflect when batch analysis has completed.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, python
- Bereich
- api
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 55/100