You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that a similarity search on one provided index also returned results from another index, but not always. After some testing I figured out that this occurs, when the index names are similar, or to be more specific, if the name of the searched index is a prefix of the other index, which should not be searched on.
Example:
Index 1: "apple"
Index 2: "applejuice"
If I now connect to Index #1 and perform a search, I get results from #1 as well as #2. However, when I search on #2 I only get results from 'applejuice', since its name is not a prefix of #1.
Anyone else noticed/aware of that? Now that I know I make sure the index names are not too simple, but at least while prototyping I might come across this when I can't be bothered to have a long/complex name.
Cheers!
The text was updated successfully, but these errors were encountered:
I've noticed that a similarity search on one provided index also returned results from another index, but not always. After some testing I figured out that this occurs, when the index names are similar, or to be more specific, if the name of the searched index is a prefix of the other index, which should not be searched on.
Example:
If I now connect to Index #1 and perform a search, I get results from #1 as well as #2. However, when I search on #2 I only get results from 'applejuice', since its name is not a prefix of #1.
Anyone else noticed/aware of that? Now that I know I make sure the index names are not too simple, but at least while prototyping I might come across this when I can't be bothered to have a long/complex name.
Cheers!
The text was updated successfully, but these errors were encountered: