An order of fields in HTTP API aggregation request affect results

[Nick-S-2018]

Bug Description:

Setting the sort key before the terms key inside the aggs node leads to an error. If the order is opposite, all works fine.

curl -X GET localhost:9308/cli -d 'create table test(f int)'
Query OK, 0 rows affected (0.012 sec)

curl -sX POST http://localhost:9308/search -d '  
{
   "index":"test",
   "aggs":{
      "group_property":{
         "terms":{
            "field":"f"
         },                
         "sort":[
            {   
               "count(*)":{
                  "order":"desc"
               }
            }           
         ]
      }
   }   
}'
{"took":0,"timed_out":false,"hits":{"total":0,"total_relation":"eq","hits":[]},"aggregations":{"group_property":{"buckets":[]}}}

curl -sX POST http://localhost:9308/search -d '  
{
   "index":"test",
   "aggs":{
      "group_property":{
         "sort":[
            {
               "count(*)":{
                  "order":"desc"
               }
            }
         ],
         "terms":{
            "field":"f"
         }
      }
   }
}'
{"error":"\"aggs\" bucket 'group_property' should be an object"}

Manticore Search Version:

Manticore 6.3.3 1de3cb364@24062617 dev

Operating System Version:

Ununtu 22.04 LTS

Have you tried the latest development version?

Yes

Internal Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

• Implementation completed
• Tests developed
• Documentation updated
• Documentation reviewed
• Changelog updated

[sanikolaev]

@Nick-S-2018 does this issue block anything?

[Nick-S-2018]

No, it doesn't.

[leessmin]

I also encountered this problem, the key is the go language map can not be adjusted to follow the order of the headache