#๐ฑ _๐๐ผ๐๐ฟ๐ฐ๐ฒ:
_source contains the actual documents that you ingested in elasticsearch.
Finally, the user sees the ingested documents that is _source.
Note: Lucene maintains its own "id" for its processing. Do not confuse DocId's with "_id".
What happens when a full-text search is performed using the "match" query in Elasticsearch?
Understanding this Will Benefit in:
a. Writing better queries
b. Debugging the queries
c. Evaluating the results.
d. Avoiding Random guesses & solving problem with process
Let's dive in.
#๐ฐ ๐ฃ๐ผ๐๐๐ถ๐ป๐ด ๐๐ถ๐๐:
A list of DocId's that contains a particular Term
In case of "magic" term, let's say "magic" is present in 2 documents having document Id 1 & 10. so posting the list for the term "magic" looks like
magic => [1,10]
Alright, letโs hit pause on these YouTube videos.
Ingredients we have so far: limited memorization, hook, mystery, climax, time dilation, and a hero.
The hardest problem in computer science is people; the second hardest problem is designing systems that are able to evolve & adapt to new goals & constraints over a span of many years or even decades
@HBOMaxHelp Dear Intern,
I once was working in prod server, I mistakenly executed "rm -rf" command in the /etc folder, And it brought all the prod application down. Yes we exists.
AS I had a good team and a compassionate manager, They came to my rescUe.
We mistakenly sent out an empty test email to a portion of our HBO Max mailing list this evening. We apologize for the inconvenience, and as the jokes pile in, yes, it was the intern. No, really. And weโre helping them through it. โค๏ธ