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

[PR #27] [MERGED] Astra DB notebooks allow optional namespace specification #629

New Issue
Closed
opened 2026-02-16 00:18:39 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 00:18:39 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_cloud_services/pull/27
Author: @hemidactylus
Created: 2/21/2024
Status: ✅ Merged
Merged: 2/28/2024
Merged by: @jerryjliu

Base: main ← Head: SL-namespaces-in-astra-db-examples

📝 Commits (1)

  • 371eae4 Astra DB notebooks allow optional namespace specification

📊 Changes

2 files changed (+7 additions, -2 deletions)

View changed files

📝 examples/demo_advanced_astradb.ipynb (+4 -1)
📝 examples/demo_astradb.ipynb (+3 -1)

📄 Description

With this PR, the Astra DB notebooks have the option of specifying a namespace (if not specified, the default namespace is used).

This matches the new feature on the Astra UI to manage custom namespaces in one's database.

(The notebooks remark that the namespace should exist already on DB when provisioning the vector stores.)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/llama_cloud_services/pull/27 **Author:** [@hemidactylus](https://github.com/hemidactylus) **Created:** 2/21/2024 **Status:** ✅ Merged **Merged:** 2/28/2024 **Merged by:** [@jerryjliu](https://github.com/jerryjliu) **Base:** `main` ← **Head:** `SL-namespaces-in-astra-db-examples` --- ### 📝 Commits (1) - [`371eae4`](https://github.com/run-llama/llama_cloud_services/commit/371eae4e2d9e36a09c11d592d0075e3e769a7801) Astra DB notebooks allow optional namespace specification ### 📊 Changes **2 files changed** (+7 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `examples/demo_advanced_astradb.ipynb` (+4 -1) 📝 `examples/demo_astradb.ipynb` (+3 -1) </details> ### 📄 Description With this PR, the Astra DB notebooks have the option of specifying a namespace (if not specified, the default namespace is used). This matches the new feature on the Astra UI to manage custom namespaces in one's database. _(The notebooks remark that the namespace should exist already on DB when provisioning the vector stores.)_ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 00:18:39 -05:00
yindo closed this issue 2026-02-16 00:18:39 -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 pull-request
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#629
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?