PR #21386: fix(azureaisearch): preserve falsy metadata values in index mapping

• Repository: run-llama/llama_index
• Author: ibrahim1023
• State: open | merged: False
• Link: https://github.com/run-llama/llama_index/pull/21386

Description (problem / solution / changelog)

PR Title

fix(azureaisearch): preserve falsy metadata values in index mapping

PR Body

Description

Preserves falsy metadata values when mapping metadata fields into Azure AI Search index documents.

Previously, _default_index_mapping() only wrote metadata fields when the value was truthy, which caused valid values like 0, "", and [] to be dropped before indexing. This change updates the check to preserve all values except None and adds a regression test covering those falsy cases.

Fixes #21385

New Package?

Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

• Yes
• No

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

• Yes
• No

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• I added new unit tests to cover this change
• I believe this change is already covered by existing unit tests

Targeted test run:

uv run --directory llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch pytest tests/test_azureaisearch.py -k preserves_falsy_metadata_values

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added Google Colab support for the newly added notebooks.
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I ran uv run make format; uv run make lint to appease the lint gods

Changed files

• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/llama_index/vector_stores/azureaisearch/base.py (modified, +1/-1)
• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/tests/test_azureaisearch.py (modified, +42/-0)

PR #21387: fix(azureaisearch): falsy metadata stored as None in Azure AI Search

• Repository: run-llama/llama_index
• Author: jasiecky
• State: open | merged: False
• Link: https://github.com/run-llama/llama_index/pull/21387

Description (problem / solution / changelog)

Description

Fixed falsy metadata stored as None in Azure AI Search.

Fixes #21385

New Package?

Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

• Yes
• No

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

• Yes
• No

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

• I added new unit tests to cover this change
• I believe this change is already covered by existing unit tests

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added Google Colab support for the newly added notebooks.
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I ran uv run make format; uv run make lint to appease the lint gods

Changed files

• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/llama_index/vector_stores/azureaisearch/base.py (modified, +1/-1)
• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/pyproject.toml (modified, +1/-1)
• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/tests/test_azureaisearch.py (modified, +41/-0)
• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/uv.lock (modified, +3063/-3063)

PR #21388: fix: preserve falsy metadata values in Azure AI Search vector store

• Repository: run-llama/llama_index
• Author: voidborne-d
• State: open | merged: False
• Link: https://github.com/run-llama/llama_index/pull/21388

Description (problem / solution / changelog)

Problem

Falsy metadata values (0, "", [], False) are silently dropped when building the Azure AI Search index document.

The current truthiness check on line 899:

if metadata_value:

skips any value that evaluates to False in a boolean context, which includes valid values like integer 0, empty strings, and empty lists.

Fix

Replace the truthiness check with an explicit None check:

if metadata_value is not None:

This ensures only truly absent metadata keys are skipped, while all valid falsy values are preserved in the index.

Reproducing

1. Create an Azure AI Search index with an integer metadata field
2. Add a node with that metadata field set to 0
3. Retrieve the node — the value comes back as None instead of 0

Fixes #21385

Changed files

• llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch/llama_index/vector_stores/azureaisearch/base.py (modified, +1/-1)