ElasticSearch - index and store attributes of string field in explicit mapping

Question

I'm writting this post because i am new ES user and i am not sure if i understand correctly index and store attributes of string fields in explict mapping.

I want to have an ES index which contans list of internet sites. The document type "site" has 3 fields: url, content, inner_note

I will be searching documents which contains given phrases in "content" field. I will be retrieving single document which has particular url in "url" field. The field "inner_note" is only for my internal use and i will not use this field to searching/retrieving documents.

I prepared following mapping:

"site" : {
    "properties" : {
        "url" : {"type" : "string","store" : "no", "index" : "not_analyzed"},
        "content" : {"type" : "string", "store" : "yes", "index" : "analyzed"},
        "inner_note" : {"type" : "string","store" : "no", "index" : "no"}
    }

and i have following questions:

Have i choosed optimal "store" and "index" attributes for my scenario?
Is retrieving document by url field as fast as i would retrieve by ID? Comparing to traditional SQL version: if i want to retrieve single row in SQL table by WHERE url = ? i would create SQL index on url column.

I would be grateful for any help!

what is site is it index name or type name or what ??

Sudhanshu Gaur
– Sudhanshu Gaur

2015-09-20 18:45:49 +00:00
Commented Sep 20, 2015 at 18:45 — Sudhanshu Gaur
– Sudhanshu Gaur, Commented Sep 20, 2015 at 18:45

javanna · Accepted Answer · 2013-07-04 21:40:27Z

3

The mapping that you posted looks good for your usecase.

You want to search on both url and content, thus they are indexed (default). Url is not analyzed while content is, so that you can run full-text queries on it.

The third field is neither indexed nor stored, but you can still get it back as part of the _source field, which contains the whole document that you submitted.

Retrieving a document by id is the same as retrieving it by url in your case, since the field is not analyzed. IN fact id is internally a non analyzed field in the lucene document, exactly like the url field.

answered Jul 4, 2013 at 21:40

javanna

60.4k14 gold badges147 silver badges125 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Pajak Leon Over a year ago

Thank you very much for clear answer. I have one more question: do i have to set store = yes for "content" field if i want to run fun-text queries on it? I thought i have to, but yesterday i read few topics on stackoverflow and i am not sure right now :)

javanna Over a year ago

No you just need to index it, which is enabled by default. To keep it short you only need store:yes if you disable the _source field and you want to retrieve a field in the search results.

ramseykhalaf Over a year ago

Have a read of this answer on what the store and index parameters do if you want to know more...

Collectives™ on Stack Overflow

ElasticSearch - index and store attributes of string field in explicit mapping

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related