Skip to content

FAQ.md

Latest commit

 

History

History
29 lines (15 loc) · 1.47 KB

FAQ.md

File metadata and controls

29 lines (15 loc) · 1.47 KB

FAQ

Why does query return FLOW_GATE?

On Alliance setups (resolveAllianceConfig / CLI), call suggest_query_params for that namespace first (within the cache TTL), or use guided_query, which performs suggestion internally. On core setupCoreServer / resolveConfig, the gate is off by default; if you enabled it (PINECONE_DISABLE_SUGGEST_FLOW=false), you need suggest_query_params or must switch to Alliance tools.

Does keyword_search need suggest_query_params?

No. Only query, count, and query_documents are gated.

What happened to query_fast / query_detailed?

They are unified into query with preset: fast, detailed, or full. See MIGRATION.md.

How do I disable the suggest gate for testing?

Core: gate is already off via resolveConfig default. Alliance: set PINECONE_DISABLE_SUGGEST_FLOW=true or pass --disable-suggest-flow. Prefer fixing the client flow in production when using Alliance.

Where are benchmarks?

There is a npm run benchmark script (benchmarks/latency.ts); published README claims remain qualitative until benchmark results are checked in.

Which field is the document id?

Use document_id on rows. paper_number is a deprecated alias scheduled for removal in the next major release.

Node version errors with Vitest

Use Node ≥ 20.12 — Vitest 4’s bundler and @vitest/coverage-v8 require newer node:util / inspector APIs.