-
### Is your feature request related to a problem? Please describe
Aggregations are the most used query type in observability use cases and the aggregation is typically on metrics, request logs, etc…
-
### Problem description
Sorry if this is a duplicate, but I did not find anything related by searching in the issue tracker.
Is there any plan regarding supporting simple aggregations (like min or…
-
We're iterating every response for every filter. How can we reduce this?
- [ ] Smarter indexing: [Segment Trees](https://hackernoon.com/practical-data-structures-for-frontend-applications-when-to-u…
-
What is the expected behavior when only a _single_ input occurs within a window? We're trying to run a simple sum aggregation over some events with long-tail of infrequent events (and a smaller number…
-
### Is your feature request related to a problem? Please describe
In general there is no support of the aggregations inside the OpenSearch for now. Reference is available [here](https://opensearch.or…
-
Currently, a quirk of how we coerce types allows for running Date and Numeric aggregations (e.g. DateHistogram and Histogram) over boolean field types. This will coerce the boolean into a number, whi…
-
Currently it is possible to mix `nested` and `filter(s)` aggregations in such a way that the `filter` aggregation matches documents that are not in the same scope as its parent aggregation, which can …
-
There are sometimes extra letters for `terms` and for `percentiles` aggregations in the elasticsearch response.
Something like this happens:
`sterms#aggName`
-
## Problem
Here's a use case it would be awesome for Prisma to support:
I have 3 models:
- Users
- Follows - users can follow other users. This is a one way relationship between two users (Fol…
-
it looks like there's a ton of boilerplate involved in creating an aggregation function. `aggregate` is substantially identical across first_string, last_string, top_string; `evaluate` is identical a…