Hacker News new | past | comments | ask | show | jobs | submit login
Understand Lucene to Understand ElasticSearch (medium.com/guilherme.lb)
25 points by guilhermelb on June 20, 2020 | hide | past | favorite | 10 comments



This is the barest overview of license indexes and no relation to elastic search except a summary sentence at the bottom. If you have ever opened an indexreader in license you know more than this article


This is why I always skip medium articles. They often feature low effort content, and the experience is filled with annoying popovers or prompts.


Lol...came here to say the same thing. Beat me to it.


Do you guys have some more enlightening resources? Thanks.


Any lucene book ever


It seems like English is this person's second language and writing a blog is a good way to practice. However, there are quite a few spelling and grammar errors. I can really recommend "English Grammar in Use" by Raymond Murphy on the subject. It is impeccable until the intermediate level and "Essential Grammar in Use" is great for advanced speakers.


Probably best way is to spin up your own Elastic stack locally and attempt to import And search a very large data set.


all the slight differences between lucene, lucene ports, Solr, ElasticSearch - thats the reason it will die. any reasonable database ecosystem just has enough velocity to kill it in the medium, if not short-, term. e.g. postgres with json fields.


The Lucene ecosystem has been around since the early 2000s.. it's old enough to vote if not drink.

Maybe eventually RDBMS systems will have full-text search out of the box that makes it unnecessary, but until they do, any predictions of death are certainly premature. (also, the lifecycle of indexed documents is different enough from transactional records that it's not as easy as it sounds).


Pardon me, but a statement like this shows you either didn't use ElasticSearch/Solr/Lucene to extent to understand how it works, or you haven't used Postgres for serious full-text search.

Every tool has its place. Postgres works wonderfully in 90% of user-joe cases, but when you start to shovel in TBs of data, you'll need to look for something else.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: