langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 12:25:55 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3588] [MERGED] Add guide for bulk export to bigquery #3628

New Issue
Closed
opened 2026-06-05 18:23:44 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:23:44 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3588
Author: @katmayb
Created: 4/15/2026
Status: ✅ Merged
Merged: 5/5/2026
Merged by: @katmayb

Base: main ← Head: big-query-bulk-export

📝 Commits (2)

  • a71ef52 Add bulk export to bigquery setup guide
  • 1ffadca sidebar update

📊 Changes

2 files changed (+272 additions, -1 deletions)

View changed files

📝 src/docs.json (+2 -1)
➕ src/langsmith/big-query-bulk-export.mdx (+270 -0)

📄 Description

Fixes DOC-531

Adds a new how-to page (langsmith/big-query-bulk-export) documenting how to export LangSmith trace data to BigQuery via GCS bulk export.

Full setup: creating a GCS bucket and service account, generating HMAC keys for the S3-compatible API, creating a bulk export destination and job, and loading the resulting Hive-partitioned Parquet files into BigQuery. Step 6 covers both options for getting data into BigQuery: external tables (query in place from GCS) and native tables (copy into BigQuery storage) with console-based instructions for each.

Guide tested.

Preview

https://langchain-5e9cc07a-preview-bigque-1776354254-0662958.mintlify.app/langsmith/big-query-bulk-export

🔄 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/langchain-ai/docs/pull/3588 **Author:** [@katmayb](https://github.com/katmayb) **Created:** 4/15/2026 **Status:** ✅ Merged **Merged:** 5/5/2026 **Merged by:** [@katmayb](https://github.com/katmayb) **Base:** `main` ← **Head:** `big-query-bulk-export` --- ### 📝 Commits (2) - [`a71ef52`](https://github.com/langchain-ai/docs/commit/a71ef5206e457cf9df7b45baa14aa0efa007b05d) Add bulk export to bigquery setup guide - [`1ffadca`](https://github.com/langchain-ai/docs/commit/1ffadcac4aa6498e72674454ae8047306a423bf1) sidebar update ### 📊 Changes **2 files changed** (+272 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/docs.json` (+2 -1) ➕ `src/langsmith/big-query-bulk-export.mdx` (+270 -0) </details> ### 📄 Description Fixes DOC-531 Adds a new how-to page (langsmith/big-query-bulk-export) documenting how to export LangSmith trace data to BigQuery via GCS bulk export. Full setup: creating a GCS bucket and service account, generating HMAC keys for the S3-compatible API, creating a bulk export destination and job, and loading the resulting Hive-partitioned Parquet files into BigQuery. Step 6 covers both options for getting data into BigQuery: external tables (query in place from GCS) and native tables (copy into BigQuery storage) with console-based instructions for each. Guide tested. ## Preview https://langchain-5e9cc07a-preview-bigque-1776354254-0662958.mintlify.app/langsmith/big-query-bulk-export --- <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-06-05 18:23:44 -04:00
yindo closed this issue 2026-06-05 18:23:44 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
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: langchain-ai/docs#3628
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?