Metadata filtering in vector stores in LangChain - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does metadata filtering affect search results in LangChain vector stores?

Consider a LangChain vector store with documents tagged by metadata such as {"category": "science"} or {"category": "history"}. If you apply a metadata filter {"category": "science"} during a similarity search, what will be the effect on the search results?

A The search will return documents whose metadata category is not "science".

B The search will return only documents whose metadata category is exactly "science".

C The search will ignore metadata and return all documents matching the query.

D The search will return documents from all categories but rank "science" documents higher.

💡 Hint

Think about how filtering narrows down the pool of documents before similarity is calculated.

Metadata filtering restricts the search to only those documents that match the filter criteria exactly. Here, only documents with category = "science" are considered for similarity search.

📝 Syntax

intermediate

Which code snippet correctly applies metadata filtering in LangChain's FAISS vector store?

Given a FAISS vector store instance faiss_store, which code correctly performs a similarity search with a metadata filter {"type": "article"}?

A faiss_store.similarity_search(query, k=5, filters={"type": "article"})

B faiss_store.similarity_search(query, k=5, metadata_filter={"type": "article"})

C faiss_store.similarity_search(query, k=5, filter={"type": "article"})

D faiss_store.similarity_search(query, filter={"type": "article"}, k=5)

💡 Hint

Check the official LangChain method signature for similarity_search and the parameter name for filtering.

The similarity_search method accepts a filter parameter to specify metadata filtering. The correct parameter name is filter, not metadata_filter or filters.

🔧 Debug

advanced

Why does this metadata filter cause no results to return?

Given this code snippet:

results = vector_store.similarity_search("climate change", k=3, filter={"topic": "environment"})

But results is always empty, even though documents with topic: "environment" exist. What is the most likely cause?

A The metadata keys in the documents are capitalized, e.g., "Topic" instead of "topic", causing the filter to fail.

B The filter parameter must be a list of dictionaries, not a single dictionary.

C The similarity_search method does not support filtering by metadata.

D The vector store index is corrupted and cannot return any results.

💡 Hint

Check if the metadata keys match exactly in case and spelling.

Metadata filtering is case-sensitive. If the stored metadata keys differ in case from the filter keys, no documents match and results are empty.

❓ state_output

advanced

What is the number of documents returned after filtering and searching?

A vector store contains 10 documents: 6 have metadata {"lang": "en"} and 4 have {"lang": "fr"}. A similarity search is done with k=5 and filter {"lang": "fr"}. How many documents will the search return?

A 4 documents, all with metadata <code>{"lang": "fr"}</code>.

B 5 documents, mixed languages.

C 5 documents, all with metadata <code>{"lang": "fr"}</code>.

D 10 documents, ignoring the filter.

💡 Hint

Remember the filter limits the search pool before selecting top k.

The filter restricts the search to only 4 documents with lang = "fr". Since k=5 but only 4 match, only those 4 are returned.

🧠 Conceptual

expert

Why is metadata filtering important in vector store similarity searches?

Which of the following best explains the main benefit of using metadata filtering in vector store similarity searches?

A It merges multiple vector stores into one for combined searching.

B It changes the vector embeddings to better match the query semantics.

C It automatically corrects spelling errors in the query before searching.

D It reduces the search space to relevant documents, improving search speed and result relevance.

💡 Hint

Think about how filtering affects which documents are considered for similarity.

Metadata filtering narrows down the documents to those relevant by metadata, which speeds up search and improves relevance by excluding unrelated documents.

Practice

1. What is the main purpose of metadata filtering in vector stores?

easy

A. To delete irrelevant data from the vector store

B. To increase the size of the vector store

C. To speed up vector calculations without filtering

D. To narrow search results using extra information about data

Solution

1. Step 1: Understand metadata filtering concept

   Metadata filtering uses extra information (metadata) to limit search results to relevant items.

2. Step 2: Identify the main purpose

   The main goal is to narrow down results, not to delete data or speed up calculations without filtering.

3. Final Answer:

   To narrow search results using extra information about data -> Option D

4. Quick Check:

   Metadata filtering = Narrow search results [OK]

Hint: Metadata filters results by extra info, not by size or speed [OK]

Common Mistakes:

• Confusing filtering with deleting data
• Thinking metadata speeds up vector math alone
• Believing filtering increases store size

2. Which of the following is the correct way to apply metadata filtering in a Langchain vector store search?

easy

A. search(query, filter=[('category', 'news')])

B. search(query, filter='category=news')

C. search(query, filter={'category': 'news'})

D. search(query, filter='category:news')

Solution

1. Step 1: Recall correct filter syntax

   Langchain expects a dictionary for metadata filtering, e.g., {'key': 'value'}.

2. Step 2: Match syntax to options

   Only search(query, filter={'category': 'news'}) uses a dictionary correctly; others use strings or lists incorrectly.

3. Final Answer:

   search(query, filter={'category': 'news'}) -> Option C

4. Quick Check:

   Filter syntax = dictionary format [OK]

Hint: Use dictionary for filters: filter={'key': 'value'} [OK]

Common Mistakes:

• Using string instead of dictionary for filter
• Passing list of tuples instead of dict
• Using colon syntax inside string

3. Given this code snippet using Langchain vector store:

results = vector_store.search('climate change', filter={'source': 'news', 'year': 2023})
print(len(results))

If the vector store has 10 documents with source 'news' and year 2023, and 5 with source 'news' but year 2022, what will be printed?

medium

A. 15

B. 10

C. 5

D. 0

Solution

1. Step 1: Understand filter effect

   The filter requires both 'source' = 'news' and 'year' = 2023 to match.

2. Step 2: Count matching documents

   Only 10 documents match both conditions; 5 with year 2022 do not match.

3. Final Answer:

   10 -> Option B

4. Quick Check:

   Filter matches 10 docs with both conditions [OK]

Hint: Filter matches all conditions exactly, not partial [OK]

Common Mistakes:

• Counting documents matching only one filter key
• Ignoring year condition
• Assuming filter returns all 'news' documents

4. You wrote this code but get an error:

results = vector_store.search('AI', filter=['category', 'tech'])

What is the main problem causing the error?

medium

A. Filter should be a dictionary, not a list

B. Search query must be a dictionary

C. Filter keys must be integers

D. Filter cannot be used with string queries

Solution

1. Step 1: Check filter type

   The filter parameter expects a dictionary with key-value pairs.

2. Step 2: Identify incorrect usage

   The code uses a list instead of a dictionary, causing a type error.

3. Final Answer:

   Filter should be a dictionary, not a list -> Option A

4. Quick Check:

   Filter type must be dict, not list [OK]

Hint: Always use dict for filter, not list or other types [OK]

Common Mistakes:

• Passing list instead of dict for filter
• Thinking query must be dict
• Believing filter keys must be numbers

5. You want to find documents in a Langchain vector store about 'machine learning' but only from the year 2022 or later, and with the tag 'tutorial'. Which filter dictionary correctly applies this condition?

hard

A. {'tag': 'tutorial', 'year': {'$gte': 2022}}

B. {'tag': 'tutorial', 'year': 2022}

C. {'tag': ['tutorial'], 'year': 2022}

D. {'tag': 'tutorial', 'year': [2022, 2023, 2024]}

Solution

1. Step 1: Understand filtering for range conditions

   To filter for year 2022 or later, a comparison operator like '$gte' (greater than or equal) is needed.

2. Step 2: Analyze options for correct syntax

   {'tag': 'tutorial', 'year': {'$gte': 2022}} uses {'year': {'$gte': 2022}} which correctly expresses the condition; others do not support range filtering properly.

3. Final Answer:

   {'tag': 'tutorial', 'year': {'$gte': 2022}} -> Option A

4. Quick Check:

   Use comparison operators for range filters [OK]

Hint: Use {'key': {'$gte': value}} for filtering ranges [OK]

Common Mistakes:

• Using exact value instead of range operator
• Passing list instead of operator for year
• Misunderstanding how to filter numeric ranges