gchq / gchq/sleeper

Remove RANGE as a job report type allow start-time/end-time on other report types

Open
#8,061 0 comments 0 reactions 0 assignees View on GitHub
enhancement needs-refinement
Dominant language
Java
Stars
107
Forks
29
Avg merge
19h 46m
Merged PRs (30d)
141

Description

### User Story

As a user,
I want be able to query various reports with a range time frame,
so that i receive details of the report relevant only to that window.

### Description / Background

Presently querying for a range within the reports is done with a type of query itself "JobQuery.Type.RANGE", however this functionality wants to be adjusted to allow for ranges to be provided on the other query types.
This will make the range query redundant as it will behave the same as ALL after change so can be removed.

### Acceptance Criteria

Gherkin format example:

**Given** I set start-time and end-time on a query
**When** that query executes
**Then** the results will be limited to the range provided.

**Given** I don't set start-time and end-time on a query
**When** that query executes
**Then** the results will be limited 4 hour period from the query time.

### Technical Notes / Implementation Details

NEED TO EXPAND FUNCTIONAL CHANGES

### Dependencies / Blockers

Blocked by: https://github.com/gchq/sleeper/issues/7837
Blocked by: https://github.com/gchq/sleeper/issues/7838
Blocked by: https://github.com/gchq/sleeper/issues/7839

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the JobQuery.Type.RANGE handling and the three blocked issues, which are prerequisites for this change. Trace how report queries apply start-time and end-time, then define the affected report types and their default four-hour behavior. Done means ranges work on the other query types, RANGE is removed, and both acceptance scenarios are covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.