[PR #2128] [MERGED] chore: clarify that we index up to 100 keys per run for input/output kv #2159

Closed
opened 2026-02-17 17:23:07 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2128
Author: @samnoyes
Created: 1/7/2026
Status: Merged
Merged: 1/7/2026
Merged by: @katmayb

Base: mainHead: sam/clarify-inputs-outputs-kv-limits


📝 Commits (1)

  • ad21461 chore: clarify that we index up to 100 keys per run for input/output kv

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 src/langsmith/filter-traces-in-application.mdx (+1 -1)

📄 Description

Overview

People were confused by what this "100 key limit" meant - is it per project? per deployment? etc. Its actually per run.

Type of change

Type: Update existing documentation

Related issues/PRs

N/A

  • GitHub issue: N/A
  • Feature PR: N/A

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

Additional notes

Confirmed with Suraj that this is true


🔄 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/2128 **Author:** [@samnoyes](https://github.com/samnoyes) **Created:** 1/7/2026 **Status:** ✅ Merged **Merged:** 1/7/2026 **Merged by:** [@katmayb](https://github.com/katmayb) **Base:** `main` ← **Head:** `sam/clarify-inputs-outputs-kv-limits` --- ### 📝 Commits (1) - [`ad21461`](https://github.com/langchain-ai/docs/commit/ad2146178a832f26847ab8dea33e9e8f3523c6f4) chore: clarify that we index up to 100 keys per run for input/output kv ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/filter-traces-in-application.mdx` (+1 -1) </details> ### 📄 Description ## Overview People were confused by what this "100 key limit" meant - is it per project? per deployment? etc. Its actually per run. ## Type of change **Type:** Update existing documentation ## Related issues/PRs N/A - GitHub issue: N/A - Feature PR: N/A <!-- For LangChain employees, if applicable: --> - Linear issue: N/A - Slack thread: https://langchain.slack.com/archives/C075MG11VJB/p1767387619024319?thread_ts=1766002332.074219&cid=C075MG11VJB ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed ## Additional notes Confirmed with Suraj that this is true --- <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-17 17:23:07 -05:00
yindo closed this issue 2026-02-17 17:23:07 -05:00
yindo changed title from [PR #2128] chore: clarify that we index up to 100 keys per run for input/output kv to [PR #2128] [MERGED] chore: clarify that we index up to 100 keys per run for input/output kv 2026-06-05 18:16:58 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#2159