What if one of the fields I want to filter in Bedrock Invoke API doesnt exist in metadata file itself

Question

When using the invoke agent API of bedrock, if in the filters I include a field to filter on but this field doesnt even exist in the metadata file. Will it 
1)throw up an error or 
2)return all files where that field doesnt exist or
3) returns only those files that have that field present and also satisfies the condition 
for the 
a)NOT EQUALS operator 
b)EQUALS operator

re:Post Agent · Accepted Answer

For the NOT EQUALS operator:
If you use the notEquals filter for a field that doesn't exist in the metadata, it will return all documents where that field is not present. This is because the condition "not equal to" is satisfied when the field doesn't exist at all.

For the EQUALS operator:
If you use the equals filter for a field that doesn't exist in the metadata, it will not return any documents. This is because no documents can satisfy the condition of being equal to a value for a non-existent field.

It's important to note that the API doesn't throw an error when filtering on non-existent fields. Instead, it processes the query based on the logic of the operators used.

To ensure more predictable results, it's generally a good practice to have consistent metadata across your documents and to be aware of which fields are actually present in your metadata before applying filters.  
**Sources**  
[RetrievalFilter - Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_RetrievalFilter.html)  
[FilterAttribute - Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_FilterAttribute.html)

What if one of the fields I want to filter in Bedrock Invoke API doesnt exist in metadata file itself

Add your answer

Relevant content