cortex
cortex copied to clipboard
Fix split range queries with wrong boundaries
What this PR does: The original splitQuery add a gap(step) between boundaries, in my point of view, we may lose some data points because of this.
We should strictly align the boundaries.
Checklist
- [x] Tests updated
- [ ] Documentation added
- [ ]
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions.
Not stale
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions.