# Rollup: field referenced by a terms group must be a \[numeric\] or \[keyword/text\] type, but found \[geo\_point\]

**URL:** <https://discuss.elastic.co/t/rollup-field-referenced-by-a-terms-group-must-be-a-numeric-or-keyword-text-type-but-found-geo-point/146036>\
**Category:** Elasticsearch\
**Created:** [August 25, 2018, 5:25pm UTC](https://discuss.elastic.co/t/rollup-field-referenced-by-a-terms-group-must-be-a-numeric-or-keyword-text-type-but-found-geo-point/146036 "2018-08-25T17:25:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Ainslie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_ainslie/32/55031_2.png) [@Paul\_Ainslie](https://discuss.elastic.co/u/Paul_Ainslie)\
**Post date:** [August 25, 2018, 5:25pm UTC](https://discuss.elastic.co/t/rollup-field-referenced-by-a-terms-group-must-be-a-numeric-or-keyword-text-type-but-found-geo-point/146036/1 "2018-08-25T17:25:17Z")

</div>

I'd like to use the `geoip.location` field in my rollup, but I get this error. Is it a bug or am I going about this the wrong way? To be honest, this is more of a nice-to-have feature for us. It's not high priority.

```auto
{
  "error": {
    "root_cause": [
      {
        "type": "remote_transport_exception",
        "reason": "[mgr-elastic-003][148.251.47.231:9300][cluster:admin/xpack/rollup/put]"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "Validation Failed: 1: The field referenced by a terms group must be a [numeric] or [keyword/text] type, but found [geo_point] for field [geoip.location];"
  },
  "status": 400
}

```

Here's the JSON I used to create the index.

```auto
{
    "index_pattern": "mediaserver_20*",
    "rollup_index": "ms_5min_v4",
    "cron": "*/10 * * * * ?",
    "page_size" :10000,
    "groups" : {
      "date_histogram": {
        "field": "@timestamp",
        "interval": "5m",
        "delay": "10m"
      },
      "terms": {
        "fields": ["account", "stream", "streamtype", "host", "http_host", "clientip_n_agent", "geoip.region_name", "geoip.country_name", "geoip.continent_code", "geoip.location", "cache_status", "response", "verb"]
      },
      "histogram": {
        "fields": ["request_time"],
        "interval": 1
      }
    },
    "metrics": [
        {
            "field": "bytes",
            "metrics": ["sum"]
        },
        {
            "field": "request_time",
            "metrics": ["avg","min","max"]
        }
    ]
}

```

---

<div class="post-metadata">

**Author:** ![polyfractal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polyfractal/32/48162_2.png) [@polyfractal](https://discuss.elastic.co/u/polyfractal)\
**Post date:** [August 28, 2018, 3:33pm UTC](https://discuss.elastic.co/t/rollup-field-referenced-by-a-terms-group-must-be-a-numeric-or-keyword-text-type-but-found-geo-point/146036/2 "2018-08-28T15:33:48Z")

</div>

Not a bug, just not supported yet. We don't support any geo datatypes in rollup right now.

---

<div class="post-metadata">

**Author:** ![Paul\_Ainslie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_ainslie/32/55031_2.png) [@Paul\_Ainslie](https://discuss.elastic.co/u/Paul_Ainslie)\
**Post date:** [August 28, 2018, 4:28pm UTC](https://discuss.elastic.co/t/rollup-field-referenced-by-a-terms-group-must-be-a-numeric-or-keyword-text-type-but-found-geo-point/146036/3 "2018-08-28T16:28:41Z")

</div>

That's cool I can live without geo datatypes.

---

<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:** [September 25, 2018, 4:28pm UTC](https://discuss.elastic.co/t/rollup-field-referenced-by-a-terms-group-must-be-a-numeric-or-keyword-text-type-but-found-geo-point/146036/4 "2018-09-25T16:28:43Z")

</div>

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