Search API queryFilter range parameter ignored — returns 0 results on v1.12.5

[romamo]

Affected module
Backend API (Elasticsearch/search endpoint)

Describe the bug
Passing a queryFilter with a range condition to GET /api/v1/search/query returns 0 hits, even when many matching records exist. The parameter is silently ignored rather than returning an error.

To Reproduce

GET /api/v1/search/query?q=*&index=table_search_index&queryFilter={"query":{"range":{"updatedAt":{"gte":1700000000000}}}}

Returns {"hits":{"total":{"value":0},...}} despite many tables having updatedAt values above the threshold.

A plain GET /api/v1/search/query?q=*&index=table_search_index without the filter returns results normally.

Expected behavior
The queryFilter range condition should be applied and filter results by the updatedAt field, returning only matching records.

Version Information

• OpenMetadata version: 1.12.5 (sandbox.open-metadata.org)

Additional context
Discovered while building a "recently modified assets" workflow using the CLI. The current workaround is to fetch all results and filter client-side on updatedAt, which is inefficient for large catalogs. The range approach is documented as valid but does not work on this version.

[Darshan3690]

Hi @romamo , @harshach , @pmbrull @PubChimps sir

I have already resolved 2 issues in this project, and I’m familiar with the search and backend modules.

🔍 Initial Analysis

It seems that the queryFilter with a range condition is not being properly applied in the Elasticsearch query builder, and is likely being ignored during request parsing or query construction.

💡 Proposed Approach
Trace how queryFilter is parsed in the search endpoint (/api/v1/search/query)
Verify if range filters are correctly mapped into Elasticsearch DSL
Fix the query builder to include range conditions for fields like updatedAt
Add validation or error handling if unsupported filters are passed
Add unit/integration tests to ensure correct behavior
🚀 Outcome

This should ensure that range-based filtering works correctly and avoids returning empty results when valid matches exist.

Please assign this issue to me. I’d be happy to take it forward.

Thanks!