Kitsune release notes 2021-02-11

Full changes since our last release.

New features:

We’ve soft launched the new version of search, which is the first tangible step to removing our dependency on an incredibly old version of ElasticSearch, and improving our search functionality.

In this release we have:

The improvements in this new version of search are many, and we’ll make a more detailed post about them once the changes to instant search are no longer behind a local storage flag.

Community contributions:

Thank you to Gaurav Ghati for fixing the broken “complete overview” link on the All Products KB dashboard in this release. Along with this fix, Gaurav has fixed a couple of bugs in previous releases, which didn’t get a mention:

If you’d also like to contribute to the project, check out our documentation.

Bugfixes:

2 Likes

A very nice update, thanks! Looks like search is working as expected right now.

1 Like
  1. Enabled new search in instant search, when a specific local storage flag is set

using
https://support.mozilla.org/zh-CN/
input “firefox” outputs 3202 results
input "火狐“ outputs 130 results
input "firefox+火狐“ outputs 3208 results

What’s the rule here?

  1. Switched the “Top Contributors - Support Forum” page to use new search, which will result in much fresher data, rather than being calculated once daily

Not all languages are listed. The search is ok for me.

  1. Switched Community Search to use new search

input “灯“ outputs correct results.
input ”xx” outputs results for “XX" as well. Is this designed?

The order of results is not clear. How are they ordered?

Thanks for the fantastic feedback!

Currently “firefox” will only match documents with “firefox” in them, and “火狐” will only match documents with “火狐” in them.

We can set up a synonym for firefox, 火狐 so that searches for “firefox”, “火狐” and “firefox 火狐” will all produce the same set of results.

Are there any other synonyms like this we’ll need to set up?

This page only lists locales with an AAQ flow set up (zh-CN is not one of them), so this is expected.

Indeed, we convert characters into their lowercase forms to allow for a search for “leo” to match “Leo”, for instance.

Theoretically the users which are the closest match to your query should be ordered above those who aren’t. In practice we might need to do a little bit of tweaking here.

Thanks for the reply.

We can set up a synonym for firefox, 火狐 so that searches for “firefox”, “火狐” and “firefox 火狐” will all produce the same set of results.

This is not what I expect. I would expect that
“firefox” gets result of exact match for “firefox”,
“火狐” gets result of exact match for “火狐”,
“firefox 火狐” gets result of exact match for “firefox 火狐”,

Isn’t this more intuitive?