Optimize validation for large datasets

**Feature request**
It would be great to have filtering for store.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_filtering` with default `false`.

Start by locating the store implementation, validation path, and configuration handling in the repository. Read how store data is currently processed and identify what filtering means for this use case. Done should include an `enable_filtering` option defaulting to `false` and a clearly defined filtered behavior, but the issue does not specify the filtering rules or relevant tests.

Written by the indexing model from the issue text.