Release filtering does not work as expected in Discover

[shruthilayaj]

Environment

SaaS (https://sentry.io/)

Version

No response

Steps to Reproduce

Filtering on multiple releases.* keys in discover does not always provide expected results particularly in multi-project environments or projects with a lot of release objects. An example would be adding a search filter like release.version:>1.0.0 release.build:>10 release.stage:adopted to a Discover query.

Expected Result

All releases that fit the above criteria.

Actual Result

Empty results or a subset of the results.

[getsentry-release]

Routing to @getsentry/visibility for triage. ⏲️

[shruthilayaj]

This happens because each of these release filters are applied independently. We query the Releases postgres table independently for each of these filters, limit the results to the first 1000 results and find the intersection of releases between the three which we then add to the snuba query's WHERE clause. In environments where there are a lot of releases (due to all/my projects being selected, large timeframe or simply because the project is deploying a lot of releases), the intersection of multiple of these postgres queries could easily be 0. Since the QueryBuilder instance has access to all the search terms, a potential solution is just to combine all the release search key conditions into one and make a single postgres query to retrieve the releases.