CODEWITHSUNDEEP
elasticsearchlucenekibana
S_R
S_R

Reputation: 503

Elasticsearch data representation

I am new to elasticsearch and I thought I will go through the 10 minutes walk through to get started. But I stumbled upon with some very basic doubts here. I am not able to figure out the data representation here. For eg. the tutorial mentions about creating an index 

curl -XPUT http://localhost:9200/shakespeare -d '
{
 "mappings" : {
  "_default_" : {
   "properties" : {
    "speaker" : {"type": "string", "index" : "not_analyzed" },
    "play_name" : {"type": "string", "index" : "not_analyzed" },
    "line_id" : { "type" : "integer" },
    "speech_number" : { "type" : "integer" }
   }
  }
 }
}
';

I understand that this is a JSON string, but beyond that I am not able to understand this representation? I am not getting what is default, what is meant by not_analyzed and so on.

Is there any standard that needs to be understood on how the data is represented before proceeding with elasticsearch? I am totally new to elasticsearch and would really appreciate if I am guided with some information/tutorial which would help me understand how to start learning this technology.

Thanks & Regards Sunil

Upvotes: 0

Views: 186

Answers (2)

John Petrone
John Petrone

Reputation: 27497

The 10 minute walk-thru is for Kibana, running on top of Elasticsearch, and IMHO is not a great place to start when getting to know ES.

Personally over the last few years I've these introductions to be helpful:

http://joelabrahamsson.com/elasticsearch-101/

http://exploringelasticsearch.com/overview.html

Overall the ES documentation is reasonably complete, looks great but can be hard to navigate thru for a novice to find exactly what you need.

Upvotes: 1

eliasah
eliasah

Reputation: 40370

I think that the main aim of the 10 minutes walk through is to give a quick demo about Kibana and not a full understanding of elasticsearch (mapping,indexing,etc.)

But if you wish to understand what's happening in that example, you might want to know how to go through the documentation.

Example :

default mapping :

Often, all types in an index share similar fields and settings. 
It can be more convenient to specify these common settings in 
the _default_ mapping, instead of having to repeat yourself every 
time you create a new type. The _default_ mapping acts as a 
template for new types. All types created after the _default_ 
mapping will include all of these default settings, unless 
explicitly overridden in the type mapping itself.

And for more details about default mapping, please refer here.

Upvotes: 1

Related Questions