Hi, Boolean fields don't support doc values yet, although there is some work in progress: https://github.com/elasticsearch/elasticsearch/pull/7961
Boolean fields are simply indexed as strings: "T" for true and "F" for false and field data would require about 2 bits per document (one to know if the document has a value, and one to store the value). That's not much but it can still use quite some memory if you have lots of memory. If/when doc values support comes to booleans, this will help move most of this memory usage to disk and the filesystem cache. On Thu, Oct 2, 2014 at 2:19 PM, Han JU <[email protected]> wrote: > Hi, > > I'm taking some time reviewing our mapping. > We've put doc_values for the fields that aggregation will be calculated. > But I'm not sure is there any benefit to do this for boolean field? > This also leads me to wonder how ElasticSearch (or Lucene) index boolean > fields? > > Some insights or readings? Thanks > > Han > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/fa01f952-e577-470e-a5d2-13e6fbd381b8%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/fa01f952-e577-470e-a5d2-13e6fbd381b8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adrien Grand -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j5cR_nBYeUsXa_bZDRs71Xmn1d_s%2B%3DjOCYCQyaKc%2B-RLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
