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

When a segment is shown, and no data is there, then show accurate error message when segment won't be archived #19011

Closed
tsteur opened this issue Mar 28, 2022 · 0 comments · Fixed by #19126
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@tsteur
Copy link
Member

tsteur commented Mar 28, 2022

To reproduce, set below config settings:

[General]
rearchive_reports_in_past_last_n_months = "last1"
rearchive_reports_in_past_exclude_segments = 1
process_new_segments_from = "editLast30"
enable_general_settings_admin = 0
enable_browser_archiving_triggering = 0
browser_archiving_disabled_enforce = 1
enable_create_realtime_segments = 0
  • Then create a segment
  • Then request a date range from 1 year ago.
  • You will see an error message like below:

image

It suggests the data may become available and it may be a problem if the message doesn't go away.

However, in reality, the data will never appear because the requested data will never be archived. That's because the segment was last edited on say 2022-01-13 08:25:22 meaning we never archive any data from before say 2021-12-13 because of the process_new_segments_from = "editLast30" setting.

Expected:
The message should make it clear why the data won't become available.

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Mar 28, 2022
@tsteur tsteur added this to the 4.10.0 milestone Mar 28, 2022
@peterhashair peterhashair self-assigned this Apr 11, 2022
@sgiehl sgiehl modified the milestones: 4.10.0, 4.11.0 May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants