run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-26 16:56:36 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

The result of the RAG example based on LlamaPaser and MongoDB is “Empty Response” #293

New Issue
Open
opened 2026-02-16 00:17:23 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 00:17:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @JiyuanAn on GitHub (Oct 11, 2024).

Describe the bug
I built the LlamaIndex, LlamaPaser, MongoDB, and Atlas CLI environments locally according to the Readme file, and tried to run the "demo_mongodb.ipynb" example in the Github project. Unfortunately, "Empty Response" was output in the "Test Query" link (Figure 1). I think my operation is correct because I can see the saved data in the corresponding deployment of MongoDB Compass (Figure 2), and when I run the MongoDB example the correct results are returned (Figure 3).

Screenshots
f1
Figure 1

f2
Figure 2

f3
Figure 3

Files
attention.pdf

Client:
Please remove untested options:

  • Python Library

Additional context
Ubuntu: 22.04
MongoDB: 8.0.0
Using Mongosh: 2.3.2

Originally created by @JiyuanAn on GitHub (Oct 11, 2024). **Describe the bug** I built the LlamaIndex, LlamaPaser, MongoDB, and Atlas CLI environments locally according to the Readme file, and tried to run the "demo_mongodb.ipynb" example in the Github project. Unfortunately, "Empty Response" was output in the "Test Query" link (Figure 1). I think my operation is correct because I can see the saved data in the corresponding deployment of MongoDB Compass (Figure 2), and when I run the [MongoDB example](https://www.mongodb.com/zh-cn/docs/atlas/cli/current/atlas-cli-deploy-fts/#std-label-atlas-cli-fts-index-query) the correct results are returned (Figure 3). **Screenshots** ![f1](https://github.com/user-attachments/assets/564fef56-1db5-4ddb-a7c8-ee1cda1f45e8) Figure 1 ![f2](https://github.com/user-attachments/assets/e3249af7-667c-4781-b059-e5b25a1f1ea4) Figure 2 ![f3](https://github.com/user-attachments/assets/2fa6d896-0fa4-4c99-93d9-ba350ee380c8) Figure 3 **Files** [attention.pdf](https://github.com/user-attachments/files/17341141/attention.pdf) **Client:** Please remove untested options: - Python Library **Additional context** Ubuntu: 22.04 MongoDB: 8.0.0 Using Mongosh: 2.3.2
yindo added the bug label 2026-02-16 00:17:23 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#293
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?