Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: minimum time resolution #557

Merged
merged 2 commits into from
Apr 10, 2023
Merged

fix: minimum time resolution #557

merged 2 commits into from
Apr 10, 2023

Conversation

RogerHYang
Copy link
Contributor

@RogerHYang RogerHYang commented Apr 10, 2023

resolves #552

Because our granularity parameters are defined in terms of minutes and can only be integers, the smallest time range allowed is one minute. This PR sets that as the minimum for end_time - start_time.

This fixes the bug in issue:

Screenshot 2023-04-10 at 9 53 26 AM

@RogerHYang RogerHYang merged commit bee76c7 into main Apr 10, 2023
@RogerHYang RogerHYang deleted the time-resolution branch April 10, 2023 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[BUG] dimension min/max returning null for numeric dimensions for singe timestamp ingests
2 participants