Solution skill
Pinecone diagnosis: metadata filter matches nothing
Complete solution
Symptom: query with a filter returns empty but unfiltered query works. Check field names, value types, and operator shapes; one wrong type poisons the whole filter. Not the full reference manual.
TL;DR: Symptom: query with a filter returns empty but unfiltered query works. Check field names, value types, and operator shapes; one wrong type poisons the whole filter. Confirm it 1. Fetch a known record and print its metadata keys and value types.
The error
query with a filter returns empty but unfiltered query works. Check field names, value types, and operator shapes; one wrong type poisons the whole filter. Confirm it 1. Fetch a known record and print its metadata keys and value types.The fix
- Fetch a known record and print its metadata keys and value types.
- Compare each filter clause against those exact keys and types.
- Test clauses one at a time: add them incrementally until matches vanish; the last clause added is the culprit.
- Check operator shapes:
$inneeds a list,$gtneeds a number,$existsneeds a boolean. - Fix the field name or type to match what is actually stored.
- If metadata was stored with inconsistent types across records (some string, some number), re-ingest with normalized types.
- Keep a schema document for metadata fields; filters are only as reliable as the schema.
- This covers exactly what the title says: Pinecone diagnosis.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.
- You are doing a different workflow with Pinecone; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.
When to use this
- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Pinecone diagnosis.
- You want the fastest verified fix before digging through logs.
When not to use this
- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.
Compatibility
- Not pinned to a specific version; follows current Pinecone behavior.
Evidence
Pinecone's filter-by-metadata guide defines the operators ($eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, $exists, $and, $or) and their type expectations. Verified against live docs 2026-09-26.
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_FMG-gjlt41OjU53-89xtwA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pinecone diagnosis: metadata filter matches nothing <span>— Vectle</span></a>