Flashcards in Basics of Elastisearch Deck (27):
At it's core, Elastisearch is a:
Document oriented search engine
Options for documents in Elastisearch
The best analogy for a elastisearch is
the index section of a textbook
The basis of a elastisearch technology is built on top of
The underlying data structure for elastisearch is known as
Maps words to actual documents locations of where they occur
What kind of documents does elastisearch store?
The 4 parts of an elastisearch document
How elastisearch relates to an RDS
Field => Column
Document => Row
Type => Table
Index => Database
Like a table in an RDS
Like a database in an RDS
Inserting is AKA
Indexing. Putting data into an index.
PUT basic syntax
id must be unique!
version in a document
The number of times it has been written to
Inserting/updating in a document with an existing index
Will REPLACE ALL the data and increment the version
Putting in an id that doesn't exist in a type or index will
return a found: false
HEAD request type
Will just return 200 for found or 404 for not found
T/F Documents in elastisearch are immutable
True. Updating will replace the whole thing.
To only update one part of a document
You can use a POST with a _update param: eg POST /vehicles/car/123/_update
Then wrap in doc
To delete a document
Something to note with deleting and the amount of time
It marks it as found false, but it will eventually delete it as a background job
Can you delete a type?
No because it doesn't have an appropriate handler
Doing get on a index
Will return information on the structure of the documents inside for each type
Can you delete an index?
Two main parts of a get for a document
Settings and mappings
Mappings contains all the fields inside the document
Settings includes metadata
Getting all documents in an index and type query