ClickHouse / ClickHouse/clickpy
Question: min_date / max_date
- Dominant language
- HTML
- Stars
- 155
- Forks
- 17
- Avg merge
- 7h 56m
- Merged PRs (30d)
- 9
Description
Hey!
Thank you very much for your project. It looks fantastic and is really pleasant to use.
I have a question about the filters. When I open a [dashboard](https://clickpy.clickhouse.com/dashboard/apache-airflow) without any filters, the default values are applied automatically, which makes sense.
If I open a dashboard using a [link](https://clickpy.clickhouse.com/dashboard/apache-airflow?min_date=2025-03-22&max_date=2026-06-20) with both `min_date` and `max_date` query parameters, the data is correctly limited to that interval.
However, if I provide only `min_date`, the value shown in the filter is replaced with [2011-01-01](https://clickpy.clickhouse.com/dashboard/apache-airflow?min_date=2025-03-22), while `max_date` is automatically set to today's date. It seems like `min_date` should not be overwritten and should instead use the value provided in the query parameter.
Is this the expected behavior?
Thanks! ❤️
Contributor guide
No contributing guide indexed for this repository
Research direction
Open the Apache Airflow dashboard linked in the issue, first with both date parameters and then with only min_date, and compare the filter values. Read the dashboard’s query-parameter handling and date-filter defaults; the issue does not name a file or test. Done would mean confirming the expected behavior and ensuring a supplied min_date is retained when max_date is omitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse
- Domain
- analytics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100