-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
feat(search): The aliases are now searchable. #313
feat(search): The aliases are now searchable. #313
Conversation
4af1cef
to
a992e0f
Compare
🎉 I'm not going to merge this right now, even though the search page part works perfectly, because there are other areas that use the search, and I need to determine if including aliases is what we want everywhere. For example, when creating a new entity, we do a search based on the name to see if the new entity would be a possible duplicate. I am not 100% sure yet that searching for aliases here would be okay, and it might depend on the entity type. It does say "with exactly the same name *or alias* " there, but I need to ensure that won't be a problem for certain cases. |
That's totally fine! |
I thought about this a bit more, and did some testing. First of all, my concerns over what other components it could affect were unfounded, so that's good ! Second, I think you can actually revert to a single |
@MonkeyDo That's great. If it is then yes, we can use single match query. And what about the "creating a new entity" page? |
That uses another mechanism to do the search on the database, and is unaffected by the changes in this PR. I did find an important bug however, when testing the search component in the relationship editor. |
a992e0f
to
5f04df3
Compare
5f04df3
to
87e50b4
Compare
@MonkeyDo Made the appropriate changes to the commit. Now only aliasSet.aliases is indexed and queried. |
OK, I've done more testing, and I am satisfied this PR works nicely with no undesirable side-effects ! Thank you ! |
Perfect!
…On Thu 7 Nov, 2019, 9:55 PM Monkey Do, ***@***.***> wrote:
OK, I've done more testing, and I am satisfied this PR works nicely with
no undesirable side-effects !
Thank you !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#313>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMHKOGQOETZ7AQHNTNCSILQSQ6QXANCNFSM4JIFDLIQ>
.
|
Areas are not indexed since PR #313
Problem
#BB-310 Search for entity by alias added and was not possible earlier.
Solution
Added multi_match query and indexed entity aliases in elastic search.
Areas of Impact
src/server/helpers/search.js