# Pulling values for properties that have index set to "no"

**URL:** <https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106>\
**Category:** Elasticsearch\
**Created:** [September 21, 2016, 10:40am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106 "2016-09-21T10:40:49Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdmac](https://avatars.discourse-cdn.com/v4/letter/j/958977/32.png) [@jdmac](https://discuss.elastic.co/u/jdmac)\
**Post date:** [September 21, 2016, 10:40am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/1 "2016-09-21T10:40:49Z")

</div>

Hi All,

Been reading this ([https://www.elastic.co/blog/elasticsearch-as-a-time-series-data-store](https://www.elastic.co/blog/elasticsearch-as-a-time-series-data-store)) blog post on the [Elastic.co](http://Elastic.co) site and I'm puzzled how you'd actually retrieve values stored as

```auto
"index": "no"

```

When \_source and \_all is disabled.

For instance, Kibana discover can't see the fields. The settings recognise the mappings are there.

Similarly the \_search API (as per documentation) doesn't work without indexed fields and as far as I can tell, even less so if \_all and \_source is disabled.

So how would you retrieve these values?

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [September 21, 2016, 11:16am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/2 "2016-09-21T11:16:47Z")

</div>

Hi,

good question, as you said you can't retrieve the fields with the document Get API or by searching. But refering to the blog post you mentioned, the fields that are later used in aggregations are declared as having `"doc_values": true` in the mappings. This means that for those fields the data is stored on disk using the [doc\_values](https://www.elastic.co/guide/en/elasticsearch/reference/current/doc-values.html) data structure which is optimized for use in aggregations but cannot be searched.

You can still take a look at those values using [fielddata\_fields](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/search-request-fielddata-fields.html) functionality. Here is a small example:

```auto
PUT /test
{
  "mappings": {
    "type": {
      "_all": { "enabled": false },
      "_source": { "enabled": false },
      "properties": {
        "count": {
           "type": "integer", "doc_values": true, "index": "no" }
        
      }
    }
  }
}

PUT /test/type/1
{
  "count" : 5,
  "age": 21
}

PUT /test/type/2
{
  "count" : 10,
  "age" : 13
}

GET /test/type/1

GET /test/type/_search
{
  "query": {
    "ids": {
      "values" : ["1"]
    }
  },
  "fielddata_fields": ["count"]
}

```

With the above mapping, searching for "count" e.g. with a range query will give you a exception because the field is not indexed. However, using the "ids" query to filter one (or more) documents, you can see the field data (or in this case doc\_values) of that field.

---

<div class="post-metadata">

**Author:** ![jdmac](https://avatars.discourse-cdn.com/v4/letter/j/958977/32.png) [@jdmac](https://discuss.elastic.co/u/jdmac)\
**Post date:** [September 21, 2016, 11:35am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/3 "2016-09-21T11:35:04Z")

</div>

@cbuescher - Thanks for the reply Christoph.

Ok, so I understand what you're saying and from 2.x doc\_values were default enabled - So I'm confident the data is stored.

My original post was a little bit of a loaded question leading onto the fact I'm now trying to visualize the data that has been input.

I can see in the originally linked blog post screen captures demoing visualization but for the life of me can't figure out how he achieve that, there's a large chunk of information/guidance missing from what I can tell.

Looks like I wasn't the only one... [http://engineering.laterooms.com/elasticsearch-as-a-time-series-database-part-2-getting-stats-in/](http://engineering.laterooms.com/elasticsearch-as-a-time-series-database-part-2-getting-stats-in/)

I suppose it leads on to two questions here:

1. This maybe for the Kibana forum more, but does Kibana 4.5.x now support aggregations of doc\_value fields?
2. Is it unreasonable for me to have an expectation that once the data is loaded into the index (and it's correctly mapped) that I should just be able to use Kibana or (preferred) grafana to aggregate and visualize?

Many thanks,

jdmac

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [September 21, 2016, 11:53am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/4 "2016-09-21T11:53:27Z")

</div>

> [@jdmac](#):
>
> 1. This maybe for the Kibana forum more, but does Kibana 4.5.x now support aggregations of doc\_value fields?
> 2. Is it unreasonable for me to have an expectation that once the data is loaded into the index (and it's correctly mapped) that I should just be able to use Kibana or (preferred) grafana to aggregate and visualize?

I cannot really answer that, those are indeed questions better asked to the [kibana folks](https://discuss.elastic.co/c/kibana).

---

<div class="post-metadata">

**Author:** ![jdmac](https://avatars.discourse-cdn.com/v4/letter/j/958977/32.png) [@jdmac](https://discuss.elastic.co/u/jdmac)\
**Post date:** [September 21, 2016, 11:55am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/5 "2016-09-21T11:55:05Z")

</div>

@cbuescher - Thanks again for the reply.

Unfortunately that's one annoyance of these discussion boards, having to repost topics when it crosses one member of the stack to another.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 22, 2016, 4:53am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/6 "2016-09-22T04:53:04Z")

</div>

Just move the thread then, you can do that by editing the topic and picking a new category.

---

<div class="post-metadata">

**Author:** ![jdmac](https://avatars.discourse-cdn.com/v4/letter/j/958977/32.png) [@jdmac](https://discuss.elastic.co/u/jdmac)\
**Post date:** [September 22, 2016, 5:52am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/7 "2016-09-22T05:52:13Z")

</div>

Fair point- hadn't realised you could. But still a restricting forum system  
in terms of visibility when products for discussion work so tightly in a  
stack. A better system would be topic tagging like serverfault and f5. Just  
putting my suggestion out there.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 23, 2016, 7:42am UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/8 "2016-09-23T07:42:42Z")

</div>

It's a good point!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:17pm UTC](https://discuss.elastic.co/t/pulling-values-for-properties-that-have-index-set-to-no/61106/9 "2017-07-05T22:17:50Z")

</div>