# High level rest client aggregations naming

**URL:** <https://discuss.elastic.co/t/high-level-rest-client-aggregations-naming/261458>\
**Category:** Elasticsearch\
**Created:** [January 18, 2021, 5:46pm UTC](https://discuss.elastic.co/t/high-level-rest-client-aggregations-naming/261458 "2021-01-18T17:46:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chapmantrain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chapmantrain/32/22646_2.png) [@chapmantrain](https://discuss.elastic.co/u/chapmantrain)\
**Post date:** [January 18, 2021, 5:46pm UTC](https://discuss.elastic.co/t/high-level-rest-client-aggregations-naming/261458/1 "2021-01-18T17:46:25Z")

</div>

I am building a spring boot query builder for my end users. It looks like from the discussions that I am going to have to unpack the search response before sending. It appears the client appends the class info on the aggregation name, like sterms#categories, making the json string not readable on the web page receiving end. Am I correct?

```auto
{
  "took": 1892,
  "timed_out": false,
  "_shards": {
    "total": 1232,
    "successful": 1232,
    "skipped": 1143,
    "failed": 0
  },
  "hits": {
    "total": 36694295,
    "max_score": 0,
    "hits": []
  },
  "aggregations": {
    "sterms#cats": {
      "doc_count_error_upper_bound": 86984,
      "sum_other_doc_count": 21111557,
      "buckets": [...

```

---

<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 15, 2021, 5:46pm UTC](https://discuss.elastic.co/t/high-level-rest-client-aggregations-naming/261458/2 "2021-02-15T17:46:33Z")

</div>

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