Skip to main content

Feedback needed: Aggregations for CDF Records

  • July 18, 2025
  • 2 replies
  • 40 views
T
Expert ⭐️⭐️⭐️⭐️
Forum|alt.badge.img

All,

Now that you’ve had some time to “play with” the Records feature, we’re looking to identify what the consensus is when it comes to the available aggregations for Records. 

  1. Do we have a useful mix of aggregations available in the API today?
  2. Which of the aggregates do you use most often?
  3. What is your experience with the API documentation for aggregate API endpoint so far?
  4. Have you attempted to use the movingFunction aggregate?
    1. What problem did you use it to solve for your  use case?
    2. Was the information in the documentation sufficient and useful for you?
    3. If you haven’t used the aggregate, please help us understand why not?
  5. Have you attempted to use the timeHistogram aggregate?
    1. Was the information in the documentation sufficient and useful for you?
    2. If you haven’t used the aggregate, please help us understand why not?
  6. Is there a use case involving aggregates that you have not been able to address in Records?
    1. Please describe the use case?
    2. How important is the “missing” aggregate for your desired Records use (scale of 1-10, 10 = Critical, 1 = Not important at all)

Please feel free to email me your responses directly if posting it in this private forum is too revealing for your company and use case(s).

And thank you for taking the time to test and respond!

-- Thomas

    2 replies

    Aditya Kotiyal
    MVP ⭐️⭐️⭐️⭐️⭐️
    Forum|alt.badge.img+5
    • Aditya Kotiyal
    • MVP ⭐️⭐️⭐️⭐️⭐️
    • July 31, 2025

    ​@Utkarsh Bhakne , ​@Richard Booth , ​@Cyril Guipet ,  ​@Mayur Deshpande , ​@Avdhesh Kumar Jha , ​@Tanmay Deshpande , ​@Chinmoy Mohanty , ​@Hua RUAN , ​@Jatin Sablok 

    Any feedback on the above queries.

    Aditya Kotiyal
    R
    Practitioner ⭐️
    • Richard Booth
    • Practitioner ⭐️
    • August 1, 2025
    1. I can’t think of anything else I would want.
    2. Mostly just count, with filters.
    3. Seems quite complete - some of the concepts are quite complex though and need that explanation.
    4. I think I understand the idea around this, but I can’t think of a good use case today for my application.
    5. Yes, this worked well for e.g. retrieving the number of records per week over an interval.  I think documentation could be clearer about the purpose of the first “property” field as it isn’t clearly distinguishing that this is the creation timestamp or similar that will be used to form the buckets rather than the property that will be aggregated.  Also, as would be expected, this property needs to be a Time/Date type, but this is not documented.
    6. Can’t think of any use cases that would need support for additional aggregates.
      Terms & ConditionsAccessibility statement