feat(search-issues): Make message column available for querying

[wedamija]

This allows the message column on search issues to be queried, and stops using issue_title. We won't merge this until we've dual written data for a week or two.

Relies on #4385, #4387 Related to getsentry/sentry#50345

[wedamija]

We started dual writing today, can merge in a couple weeks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.93%. Comparing base (9b40b77) to head (58791f3).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4391   +/-   ##
=======================================
  Coverage   89.93%   89.93%           
=======================================
  Files         897      897           
  Lines       43538    43552   +14     
  Branches      288      288           
=======================================
+ Hits        39155    39168   +13     
- Misses       4341     4342    +1     
  Partials       42       42           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lynnagara]

I think it's possible to add a query processor that falls back to the other column. So you can switch over immediately and keep queries simpler.

[wedamija]

I think it's possible to add a query processor that falls back to the other column. So you can switch over immediately and keep queries simpler.

Oh like a coalesce or something along those lines?

[lynnagara]

yeah, something like that. Pretty sure you can use the ColumnToFunction mapper to map the messages column to something like coalesce(nullif(message, ""), "search_title") I'm assuming here that it's ok to fall back on the search title if message is empty string. @evanh / search team might have more opinions on it though.

[evanh]

Pretty sure you can use the ColumnToFunction mapper to map the messages column to something like coalesce(nullif(message, ""), "search_title")

That isn't currently supported in the YAML right now, so you'd need to write a custom query processor and add it to the config that way. If that's something you want to do we can help with that. As long as it gets removed when the cutover is complete.