sum-bucket-aggregation.asciidoc 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114
  1. [[search-aggregations-pipeline-sum-bucket-aggregation]]
  2. === Sum Bucket Aggregation
  3. A sibling pipeline aggregation which calculates the sum across all bucket of a specified metric in a sibling aggregation.
  4. The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
  5. ==== Syntax
  6. A `sum_bucket` aggregation looks like this in isolation:
  7. [source,js]
  8. --------------------------------------------------
  9. {
  10. "sum_bucket": {
  11. "buckets_path": "the_sum"
  12. }
  13. }
  14. --------------------------------------------------
  15. // NOTCONSOLE
  16. [[sum-bucket-params]]
  17. .`sum_bucket` Parameters
  18. [options="header"]
  19. |===
  20. |Parameter Name |Description |Required |Default Value
  21. |`buckets_path` |The path to the buckets we wish to find the sum for (see <<buckets-path-syntax>> for more
  22. details) |Required |
  23. |`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
  24. details)|Optional | `skip`
  25. |`format` |format to apply to the output value of this aggregation |Optional |`null`
  26. |===
  27. The following snippet calculates the sum of all the total monthly `sales` buckets:
  28. [source,js]
  29. --------------------------------------------------
  30. POST /sales/_search
  31. {
  32. "size": 0,
  33. "aggs" : {
  34. "sales_per_month" : {
  35. "date_histogram" : {
  36. "field" : "date",
  37. "calendar_interval" : "month"
  38. },
  39. "aggs": {
  40. "sales": {
  41. "sum": {
  42. "field": "price"
  43. }
  44. }
  45. }
  46. },
  47. "sum_monthly_sales": {
  48. "sum_bucket": {
  49. "buckets_path": "sales_per_month>sales" <1>
  50. }
  51. }
  52. }
  53. }
  54. --------------------------------------------------
  55. // CONSOLE
  56. // TEST[setup:sales]
  57. <1> `buckets_path` instructs this sum_bucket aggregation that we want the sum of the `sales` aggregation in the
  58. `sales_per_month` date histogram.
  59. And the following may be the response:
  60. [source,js]
  61. --------------------------------------------------
  62. {
  63. "took": 11,
  64. "timed_out": false,
  65. "_shards": ...,
  66. "hits": ...,
  67. "aggregations": {
  68. "sales_per_month": {
  69. "buckets": [
  70. {
  71. "key_as_string": "2015/01/01 00:00:00",
  72. "key": 1420070400000,
  73. "doc_count": 3,
  74. "sales": {
  75. "value": 550.0
  76. }
  77. },
  78. {
  79. "key_as_string": "2015/02/01 00:00:00",
  80. "key": 1422748800000,
  81. "doc_count": 2,
  82. "sales": {
  83. "value": 60.0
  84. }
  85. },
  86. {
  87. "key_as_string": "2015/03/01 00:00:00",
  88. "key": 1425168000000,
  89. "doc_count": 2,
  90. "sales": {
  91. "value": 375.0
  92. }
  93. }
  94. ]
  95. },
  96. "sum_monthly_sales": {
  97. "value": 985.0
  98. }
  99. }
  100. }
  101. --------------------------------------------------
  102. // TESTRESPONSE[s/"took": 11/"took": $body.took/]
  103. // TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
  104. // TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]