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

Mesage not properly filtered by timestamp in CLG #69

Closed
haiqi96 opened this issue Aug 10, 2022 · 0 comments
Closed

Mesage not properly filtered by timestamp in CLG #69

haiqi96 opened this issue Aug 10, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@haiqi96
Copy link
Contributor

haiqi96 commented Aug 10, 2022

Bug

In CLG, the message are not properly filtered with timestamp when the timestamp range becomes small.

For example, on hadoop-24hrs-log, the following search commnad (1) returns several messages, but none of (2) or (3) returns any matched search results, although (2) and (3) cover the same exact time range as (1) so they should also return matches.

  1. clg --tge 1427099450000 --tle 1427099490000 hadoop_output/ "*"
  2. clg --tge 1427099460000 --tle 1427099490000 hadoop_output/ "*"
  3. clg --tge 1427099450000 --tle 1427099460000 hadoop_output/ "*"

Suspect that this is caused by some issues in the database queries.

CLP version

5d135cf

Environment

baker

Reproduction steps

  • compress hadoop-24hrs-log to hadoop-out
  1. clg --tge 1427099450000 --tle 1427099490000 hadoop_output/ "*"
  2. clg --tge 1427099460000 --tle 1427099490000 hadoop_output/ "*"
  3. clg --tge 1427099450000 --tle 1427099460000 hadoop_output/ "*"

The 2nd and 3rd command will not return any output. but the you should see there are message matches in the first command

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