run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-27 01:15:06 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Request Field for Logging User-Specified Job-Level metadata #261

New Issue
Open
opened 2026-02-16 00:17:18 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 00:17:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @adreichert on GitHub (Sep 9, 2024).

Summary

I'd like to request that both the REST API and the Python package offer a field that permits users to upload small, custom strings. This field would NOT be used for parsing by LlamaParse. The user could populate it with freeform strings, small JSON documents, or anything else they wanted. Later, they could read this from the job details endpoint. In the past, I've used such fields for the following:

  • Debugging
  • Tagging uploaded jobs
  • Storing identifiers useful for joining this job to other tables or data sources

Example

% curl -L -X POST 'https://api.cloud.llamaindex.ai/api/v1/parsing/upload' \      
[...]
-F 'user_metadata="DEBUG"'
[...]

 curl -L -X GET 'https://api.cloud.llamaindex.ai/api/v1/parsing/job/<ID>/details' \ 
[...]
user_metadata="DEBUG"
Originally created by @adreichert on GitHub (Sep 9, 2024). # Summary I'd like to request that both the REST API and the Python package offer a field that permits users to upload small, custom strings. This field would NOT be used for parsing by LlamaParse. The user could populate it with freeform strings, small JSON documents, or anything else they wanted. Later, they could read this from the job details endpoint. In the past, I've used such fields for the following: * Debugging * Tagging uploaded jobs * Storing identifiers useful for joining this job to other tables or data sources # Example ``` % curl -L -X POST 'https://api.cloud.llamaindex.ai/api/v1/parsing/upload' \ [...] -F 'user_metadata="DEBUG"' [...] ``` ``` curl -L -X GET 'https://api.cloud.llamaindex.ai/api/v1/parsing/job/<ID>/details' \ [...] user_metadata="DEBUG" ```
yindo added the enhancement label 2026-02-16 00:17:18 -05:00
yindo commented 2026-02-16 00:17:18 -05:00
Author
Owner
Copy Link
Copy Source

@hexapode commented on GitHub (Sep 9, 2024):

Great Feedback. We will add it to a future release (most likely in the next 2-3 weeks)

@hexapode commented on GitHub (Sep 9, 2024): Great Feedback. We will add it to a future release (most likely in the next 2-3 weeks)
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 enhancement
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#261
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?