81K views · Dec 15, 2013 · 1:04:30 · 3 HN recommenders · 3 mentions · discussed 2019–2020
Elasticsearch engineer and Lucene committer Adrien Grand explains the design decisions inside a Lucene index and what problems it can and cannot solve. The talk goes into how Lucene stores data for fast search and analytics.
Why Hacker News points people here: HN recommends it as an instructive, easy-to-follow look at Lucene internals from a core committer.
“I can super highly recommend talks by Adrien Grand on Lucene and Elasticsearch.”HN comment, 2020
“I can super highly recommend talks by Adrien Grand on Lucene and Elasticsearch.”
Instructive, easy-to-follow talks on Lucene internals
I can super highly recommend talks by Adrien Grand on Lucene and Elasticsearch. They are super instructive yet easy to follow. this video link
“A nice view of how lucene internals work by core committer Adrien Grand”
Look at Lucene internals from a core committer
This is extremely high level. A nice view of how lucene internals work by core committer Adrien Grand: link this video
“found this video really good”
Good review of Lucene concepts
This is excellent. I was recently reviewing Lucene concepts and found this video really good: this video Also this site has a series of Lucene articles that are pretty nice. The one on Term Vectors in particular: link Based on some quick research it seems like Lucene is already using a sorted skip data structure for the posting list, so I wonder why they had to do a custom implementation? Perhaps it has to do with their custom Document ID scheme and how they want to preserve order in the Posting List being different from the default behavior. It also sounds like searchers are searching on indexes as they're being written, and there is some custom coordination around visibility, which might require diverging from Lucene default behavior. Either way, pretty impressive!
