4 ms·
Not always, though: https://www.blog.google/products/search/improvements-searching-special-characters-programming-languages/ https://www.blog.google/products/se
by oktoberpaard 4y ago
Not always, though: https://www.blog.google/products/search/improvements-searching-special-characters-programming-languages/ https://www.blog.google/products/search/improvements-searchi....
- Retr0id 4y agoInteresting - looks like they're doing this via a bunch of special-case rules. To any google engineers reading: Please add `really-verbatim` mode, indicated by backtick quotes, which also requires strict matching of punctuation.
- ComodoHacker 4y agoNo way they'll inflate their indexes even 20% and add complexity into their algorithms for 0.1% queries that won't bring any additional income.
- Retr0id 4y agoThey don't necessarily have to inflate their indexes. Backtick-quoted results ought to be a subset of double-quoted results, so they can use the standard quoted search algorithm, and then filter out imperfect matches from those results.
- mkl 4y agoGoogle searches ignore punctuation, so it's not even indexed, so there's no way to search for punctuation without inflating the index
- Retr0id 4y agoRead what I said. They can use the standard index, then filter the results as a last pass.
- deleted 4y ago[deleted]
- mkl 4y agoI did read what you said. Imagine trying to search for [::] as 8192kjshad09- suggested earlier in the thread. What standard index results are you going to filter? Since "[::]" isn't in the index, you won't have anything to go on. To do your back-tick really-verbatim searches, the index has to be enlarged.
- Retr0id 4y agoAh, sorry, I see what you mean.
- dannysullivan 4y agoI work for Google Search. We did look a this, and we'll keep looking to see if we can improve, but it turns out to be a very hard lift.
- lrem 4y agoI'm a Google engineer way too far organisationally to ever have any say in this. I wonder if that will ever be worth the hardware cost. Back when I did some coursework on information retrieval, it seemed that you get superlinear savings via reducing the cardinality of tokens. So you'd do stemming, remove all punctuation, words that are too frequent ("do", "be", "and", "or", ...)... Basically remove all grammar. You do the same to your search query and the index. This intuitively reduces your compute by at least an order of magnitude, especially for languages with rich grammar (e.g. stemming nouns in Polish reduces the cardinality of tokens by a factor of 7 and verbs by a factor of 162).