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

Unexpected query failure in specific timestamp when using earliest(_time), latest(_time) aggregation #422

Open
Abigael-JT opened this issue Nov 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Abigael-JT
Copy link
Contributor

Abigael-JT commented Nov 19, 2024

Describe the bug

This query fails with an error similar to the one provided below
%dpl
index=abc earliest=2024-11-17T19:00:00+00:00 latest=2024-11-18T12:00:00+02:00
| stats count, earliest(_time), latest(_time)

However when the query is run without, earliest(_time), latest(_time, it works as expected

%dpl
index=abc earliest=2024-11-17T19:00:00+00:00 latest=2024-11-18T12:00:00+02:00
| stats count

Expected behavior

The query should return an empty table if there is no data for the specified timeframe or returns results with count, earliest(_time), latest(_time)

How to reproduce

Run this query to reproduce the issue:
%dpl
index=crud earliest=2021-01-01T19:00:00+00:00 latest=2021-12-31T12:00:00+02:00
| stats count, earliest(_time), latest(_time)

Screenshots

Error:

Job aborted due to stage failure: ...
ExecutorLostFailure ...
Reason: Container from a bad node:
....

Driver stacktrace:
Took 1 min 18 sec. Last updated

Software version

pth_10 version: 8.1.0
pth_03 version: 9.2.0

Desktop (please complete the following information if relevant):

  • OS:
  • Browser:
  • Version:

Additional context

@Abigael-JT Abigael-JT added the bug Something isn't working label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant