Describe the bug
Running piperider compare-reports --last against a dbt metric results in an error like ValueError: Invalid isoformat string: '2023-04-01 00:00:00'
To Reproduce
Steps to reproduce the behavior:
- Setup new virtual environment and run pip install
"piperider[bigquery]==0.23.3"
- Initialize Piperider with
piperider init
- Add the
piperider tag to a metric configuration file
- Run
piperider run twice to generate two reports
- Run
piperider compare-reports --last --debug
- See an error like
ValueError: Invalid isoformat string: '2023-04-01 00:00:00'
Expected behavior
The compare-reports command should create an HTML report and a Markdown report in the .piperider/comparisons/ directory
Desktop (please complete the following information):
- OS: Debian GNU/Linux
- Python Version 3.9.16
- Version: dbt 1.4.5, dbt metrics 1.4.0, piperider[bigquery]==0.23.3
Additional context
Add any other context about the problem here.
The offending metric configuration can be found below:
version: 2
metrics:
- name: total_seconds_engaged
label: Total Seconds Engaged
model: ref('fct_hits')
description: "The number of seconds readers spent viewing a page"
calculation_method: sum
expression: seconds_engaged
timestamp: date
time_grains: [day, week, month, quarter, year, all_time]
dimensions:
- article_arc_id
tags:
- piperider
The full output of piperider compare-reports --last --debug is attached:
piperider_debug.txt
Describe the bug
Running
piperider compare-reports --lastagainst a dbt metric results in an error likeValueError: Invalid isoformat string: '2023-04-01 00:00:00'To Reproduce
Steps to reproduce the behavior:
"piperider[bigquery]==0.23.3"piperider initpiperidertag to a metric configuration filepiperider runtwice to generate two reportspiperider compare-reports --last --debugValueError: Invalid isoformat string: '2023-04-01 00:00:00'Expected behavior
The
compare-reportscommand should create an HTML report and a Markdown report in the.piperider/comparisons/directoryDesktop (please complete the following information):
Additional context
Add any other context about the problem here.
The offending metric configuration can be found below:
The full output of
piperider compare-reports --last --debugis attached:piperider_debug.txt