Enable aggregates and group_by

[catalyst17]

TL;DR

Enhanced the query functionality to support multiple grouping fields and aggregations, with improved type handling for ClickHouse data types.

What changed?

• Modified GroupBy field in QueryParams to accept an array of strings instead of a single string
• Added GetAggregations method to handle grouped and aggregated queries separately
• Updated Aggregations field in QueryResponse to use []map[string]interface{} for flexible result handling
• Implemented comprehensive ClickHouse type mapping to Go types with support for nullable, array, and low cardinality types
• Separated data retrieval logic in handlers to handle aggregations distinctly from regular queries
• Added unit tests for ClickHouse type mapping functionality

How to test?

1. Query logs/transactions endpoints with multiple group_by parameters
2. Test various aggregation functions (COUNT, SUM, etc.) with grouping
3. Verify response structure for both regular and aggregated queries
4. Test handling of different ClickHouse data types and their nullable variants
5. Run new unit tests for type mapping functionality

Why make this change?

This enhancement provides more robust support for data analysis by properly handling grouped queries and aggregations. The improved type mapping system ensures accurate data representation when working with ClickHouse's various data types, while maintaining clean separation between regular queries and aggregations.

[catalyst17]

• Enable aggregates and group_by #109 👈
• Don't cut bytes from non-address topics + account for empty topics #108
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @catalyst17 and the rest of your teammates on Graphite

[catalyst17]

Merge activity

• Oct 25, 11:01 AM EDT: A user started a stack merge that includes this pull request via Graphite.
• Oct 25, 11:04 AM EDT: Graphite rebased this pull request as part of a merge.
• Oct 25, 11:05 AM EDT: A user merged this pull request with Graphite.