You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The timestamp qual is ignored, so it's pulling down all data at once (the docs say it should work)
Steampipe version (steampipe -v)
Example: Steampipe v0.21.1
Plugin version (steampipe plugin list)
Example: v0.45.0
To reproduce
Run the following query:
select log_name, receive_timestamp,timestamp, resource_type from gcp_logging_log_entry where log_name = 'projects/hsrket-aaa/logs/diagnostic-log' and timestamp <= '2023-09-29T10:09:08+05:30';
It should only fetch the results whose log entry timestamp value is less than equal to the provided timestamp instead of fetching all the results and filtering them in the steampipe level.
Expected behavior
The table should take less time if we apply any filter for the timestamp.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
The timestamp qual is ignored, so it's pulling down all data at once (the docs say it should work)
Steampipe version (
steampipe -v
)Example: Steampipe v0.21.1
Plugin version (
steampipe plugin list
)Example: v0.45.0
To reproduce
Run the following query:
It should only fetch the results whose log entry timestamp value is less than equal to the provided timestamp instead of fetching all the results and filtering them in the steampipe level.
Expected behavior
The table should take less time if we apply any filter for the timestamp.
Additional context
N/A
The text was updated successfully, but these errors were encountered: