News for hackers. Stuff that matters.
Re:Riot – Full-text search engine in Go by markpapadakis on Monday October 23, 2017 @01:34PM (#15535039)
Supporting faced search and other functionality requiring access to per document field-values is just an extension over the core IR functionality.

Tracking (document, field) values can be used for query by range or by geolocation primitives (that's what Lucene does, where it will index that data into a special tree-like structure, and for each query, it will build a custom 'iterator' and use it along with other iterators to match documents), and for static ranking of matched documents.

BTW, Lucene and Algolia are vastly different in terms of the underlying architecture.

Re:Riot – Full-text search engine in Go by lobster_johnson on Monday October 23, 2017 @01:52PM (#15535282)
What is Algolia's underlying architecture like? Are there any papers or code?
Re:Riot – Full-text search engine in Go by markpapadakis on Monday October 23, 2017 @01:54PM (#15535293)
See links about Algolia arch (and other related material) here: https://github.com/phaistos-networks/Trinity/wiki/IR-Search-...
Re:Riot – Full-text search engine in Go by gdillon on Monday October 23, 2017 @04:13PM (#15536562)
Thanks for the links, Mark! (Disclaimer, I work for Algolia.)

As Mark mentions on his summary page, the best place for that kind of information is our CTO's "Inside the Engine" series (8 parts).

https://blog.algolia.com/inside-the-algolia-engine-part-1-in...

Re:Riot – Full-text search engine in Go by Jemaclus on Monday October 23, 2017 @04:29PM (#15536696)
That's why I mentioned them separately. :)