# Different Values in Kibana Table from Kibana Discover

**URL:** <https://discuss.elastic.co/t/different-values-in-kibana-table-from-kibana-discover/294051>\
**Category:** Kibana\
**Created:** [January 11, 2022, 3:10pm UTC](https://discuss.elastic.co/t/different-values-in-kibana-table-from-kibana-discover/294051 "2022-01-11T15:10:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Avnish\_Singh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avnish_singh/32/71923_2.png) [@Avnish\_Singh](https://discuss.elastic.co/u/Avnish_Singh)\
**Post date:** [January 11, 2022, 3:10pm UTC](https://discuss.elastic.co/t/different-values-in-kibana-table-from-kibana-discover/294051/1 "2022-01-11T15:10:49Z")

</div>

Hi, I am getting a deviation in values in Kibana Visualize and Kibana Discover.  
Here is the screenshot for the value on `01-01-2022 00:00:00`

 ![start1](https://us1.discourse-cdn.com/elastic/original/3X/8/9/8907febc6b7e4de68bfe186eba12a08494abe1b2.png)

The value on `02-01-2022 00:00:00`

 ![start2](https://us1.discourse-cdn.com/elastic/original/3X/f/4/f48ea5ba80e582f750ccf1b12245b77762d96797.png)

While in the Visualization they do not tally:  
the visualization has a column `Starting Value` i.e., sorted on time in ascending order which should be for `01-01-2022 00:00:00` and the `Ending Value` sorted on time in descending order which should be for` 02-01-2022 00:00:00`. Here is the screenshot of the visualization.

 ![start3_vis](https://us1.discourse-cdn.com/elastic/original/3X/a/9/a994db13d70cad1d2fff14ed5211416dc0a7a628.png)

The query for the Visualization is:

```auto
{
  "aggs": {
    "7": {
      "terms": {
        "field": "device.keyword",
        "order": {
          "_key": "desc"
        },
        "size": 1000
      },
      "aggs": {
        "1": {
          "top_hits": {
            "docvalue_fields": [
              {
                "field": "value"
              }
            ],
            "_source": "value",
            "size": 1,
            "sort": [
              {
                "measureTime": {
                  "order": "asc"
                }
              }
            ]
          }
        },
        "2": {
          "top_hits": {
            "docvalue_fields": [
              {
                "field": "value"
              }
            ],
            "_source": "value",
            "size": 1,
            "sort": [
              {
                "measureTime": {
                  "order": "desc"
                }
              }
            ]
          }
        }
      }
    }
  },
  "size": 0,
  "fields": [
    {
      "field": "@timestamp",
      "format": "date_time"
    },
    {
      "field": "measureTime",
      "format": "date_time"
    },
    {
      "field": "persistTime",
      "format": "date_time"
    },
    {
      "field": "receiveTime",
      "format": "date_time"
    }
  ],
  "script_fields": {},
  "stored_fields": [
    "*"
  ],
  "_source": {
    "excludes": []
  },
  "query": {
    "bool": {
      "must": [],
      "filter": [
        {
          "match_all": {}
        },
        {
          "bool": {
            "minimum_should_match": 1,
            "should": [
              {
                "match_phrase": {
                  "register.keyword": "1-0:1.8.0*255"
                }
              }
            ]
          }
        },
        {
          "bool": {
            "minimum_should_match": 1,
            "should": [
              {
                "match_phrase": {
                  "group_field.current.device": "44050074"
                }
              }
            ]
          }
        },
        {
          "range": {
            "measureTime": {
              "gte": "2021-12-31T18:30:00.000Z",
              "lte": "2022-01-01T18:30:00.000Z",
              "format": "strict_date_optional_time"
            }
          }
        }
      ],
      "should": [],
      "must_not": []
    }
  }
}

```

Could anyone help me out with the reason why the same value is deviating in the visualization from discover.  
P.S: The Value in Discover is verified from cross-checking

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [January 11, 2022, 6:18pm UTC](https://discuss.elastic.co/t/different-values-in-kibana-table-from-kibana-discover/294051/2 "2022-01-11T18:18:48Z")

</div>

How is `value` indexed? It's possible the number is actually too large for its type which will cause the Visualization to return a "wrong" result because it relies on the indexed value which can't hold the full precision. Discover OTOH depending on the version will use the `_source` object to fetch the value which means it didn't go through the indexing process but instead will keep the full precision javascript will handle (64 bit floating point).

If this is the case for you, consider changing your mapping of `value` to a data type which allows for larger values.

---

<div class="post-metadata">

**Author:** ![Avnish\_Singh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avnish_singh/32/71923_2.png) [@Avnish\_Singh](https://discuss.elastic.co/u/Avnish_Singh)\
**Post date:** [January 12, 2022, 9:19am UTC](https://discuss.elastic.co/t/different-values-in-kibana-table-from-kibana-discover/294051/3 "2022-01-12T09:19:05Z")

</div>

Thanks @flash1293 for pointing out the cause of the problem.  
Great Help man

---

<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:** [February 9, 2022, 9:20am UTC](https://discuss.elastic.co/t/different-values-in-kibana-table-from-kibana-discover/294051/4 "2022-02-09T09:20:04Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.