Fix visibility full text search query in MySQL #3913
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexshtin
reviewed
Feb 8, 2023
common/persistence/visibility/store/sql/query_converter_mysql.go
Outdated
Show resolved
Hide resolved
alexshtin
approved these changes
Feb 8, 2023
rodrigozhou
force-pushed
the
fix-vis-mysql-fts
branch
from
0768fc5
to
030da3b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Added
namespace_idto full text search query expression.Why?
I added
namespace_idto FTS index to help searching when usingTexttype search attributes. But thenamespace_idis also indexed as FTS and needs to be in theMATCH() AGAINST ()expression.How did you test it?
Start local server, setup custom search attributes, and ran workflow querying
Texttype search attribute.Potential risks
No.
Is hotfix candidate?
No.