-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Issue titles for issue platform issues aren't searchable #50345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@wedamija Replays also suffers from this but on more fields than just the title. For example our events have a tag |
It looks like we don't have the search text column in ClickHouse yet, we need to write to it first |
Basically we should probably have this column in the search issues dataset in clickhouse so we can do general searches. |
…nce titles works as expected This validates that searching for an issue platform issue via text in the title works as expected. Relies on #51325 and getsentry/snuba#4385 Related to #50345
…d it initially.. Related to getsentry/sentry#50345
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
…vent search_message (#51325) We want occurrence information like title, subtitle and culprit to be searchable in clickhouse. For this to happen, we need to make sure this information is included in: - `search_message`, which is passed on to snuba to be written to the message columns - `Group.message`, which is used in the postgres side of search. Related to #50345
…nce titles works as expected This validates that searching for an issue platform issue via text in the title works as expected. Relies on #51325 and getsentry/snuba#4385 Related to #50345
* This adds the `message` column to search issues table, since we missed it initially.. Related to getsentry/sentry#50345 * remove __init__ so check stops complaining
…d it initially.. Related to getsentry/sentry#50345
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
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
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
) 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
I think this is because we're not including them in
search_message
here:sentry/src/sentry/eventstore/models.py
Lines 541 to 569 in ccfb372
We should write a test that searches on the title for a platform issue and figure out how to make it pass
The text was updated successfully, but these errors were encountered: