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

Improve error messages for Unsupported Features in cloud #1272

Open
janet-can opened this issue Apr 12, 2022 · 0 comments
Open

Improve error messages for Unsupported Features in cloud #1272

janet-can opened this issue Apr 12, 2022 · 0 comments

Comments

@janet-can
Copy link
Contributor

It would be great to have helpful error messages when something goes wrong with the soda-core soda-cloud communication. Not the connection details, but rather when something is not supported in cloud.

Using the data-council-workshop environment, running scans on checks.yml 02 and 03, with a valid, working connection to Soda Cloud, the output in the CLI indicated "Unsupported feature" and the check results do not send to the cloud.

soda scan -c configuration/configuration.yml -d workshop_ds checks/03_analyst_use_cases.yml
Soda Core 3.0.0b7
Sample test/2022-04-12 11:00:55.710523/workshop_ds/workshop_ds.failed_rows[failed rows]:
id   customer_id_nok customer_id_ok customer_country customer_zip text    date       created_at          id    size sizetxt distance pct         cat    country zip    email                  date       ts                  ts_with_tz               
---- --------------- -------------- ---------------- ------------ ------- ---------- ------------------- ----- ---- ------- -------- ----------- ------ ------- ------ ---------------------- ---------- ------------------- -------------------------
'O2' 'ID99'          'ID1'          'BE'             '2360'       'two'   2022-02-10 2022-02-24 11:25:31 'ID1' 1.0  '1'     0        '- 28,42 %' 'HIGH' 'BE'    '2360' '[email protected]' 2020-06-23 2020-06-23 00:00:10 2020-06-23 00:00:10+00:00
'O4'                 'ID1'          'BE'                          'four'  2022-02-10 2022-02-24 12:25:39 'ID1' 1.0  '1'     0        '- 28,42 %' 'HIGH' 'BE'    '2360' '[email protected]' 2020-06-23 2020-06-23 00:00:10 2020-06-23 00:00:10+00:00
'O1' 'ID1'           'ID1'          'BE'             '2360'       'one'   2022-02-10 2022-02-24 05:25:11 'ID1' 1.0  '1'     0        '- 28,42 %' 'HIGH' 'BE'    '2360' '[email protected]' 2020-06-23 2020-06-23 00:00:10 2020-06-23 00:00:10+00:00
'O6' 'ID99'          'ID1'          'UK'             '2360'       'six'   2022-02-10 2022-02-24 15:25:48 'ID1' 1.0  '1'     0        '- 28,42 %' 'HIGH' 'BE'    '2360' '[email protected]' 2020-06-23 2020-06-23 00:00:10 2020-06-23 00:00:10+00:00
'O3' 'ID1'           'ID2'          'BE'             '2000'       'three' 2022-02-10 2022-02-24 11:25:37 'ID2' 0.5  '.5'    -999     '+22,75 %'  'HIGH' 'BE'    '2361' '[email protected]' 2020-06-23 2020-06-23 00:01:10 2020-06-23 00:01:10+00:00
Sample test/2022-04-12 11:00:55.710523/workshop_ds/workshop_ds.reference[country,zip]:
id size sizetxt distance pct cat country zip email date ts ts_with_tz
-- ---- ------- -------- --- --- ------- --- ----- ---- -- ----------
Scan summary:
7/8 checks PASSED: 
    CUSTOMERS in workshop_ds
      values in (country, zip) must exist in ZIP_CODES (country, zip) [PASSED]
      Absolute average size and distance product must be < 1000000 [PASSED]
      stddev_samp(size) between 3.26 and 3.27 [PASSED]
      variance(size) between 10.65 and 10.66 [PASSED]
      var_samp(size) between 10.65 and 10.66 [PASSED]
      percentile(distance, 0.7) = 999 [PASSED]
      valid_count(pct) = 2 [PASSED]
1/8 checks FAILED: 
    High customers must have size [FAILED]
      value: 5
      failed_rows_storage_ref: {'provider': 'console', 'column_count': 20, 'total_row_count': 5, 'stored_row_count': 5, 'reference': 'Search in the console for "Sample test/2022-04-12 11:00:55.710523/workshop_ds/workshop_ds.failed_rows[failed rows]"'}
Oops! 1 failures. 0 warnings. 0 errors. 7 pass.
Sending results to Soda Cloud
> /api/command (login with API key credentials)
< 200 (login ok, token received)
Unsupported feature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant