data-quality

Thank you for this great tool!

[Describe the bug
A clear and concise description of what the bug is.]

Broken link in the automatically generated Edit Your Expectation Suite starter noteboook: https://docs.greatexpectations.io/en/latest/autoapi/great_expectations/data_asset/index.html?highlight=remove_expectation&utm_source=notebook&utm_medium=edit_expectations#great_expectations.data_

What

being able to take a data object (or prefix, like a partition) and get back the commit that added/modified it.

Why

This is valuable lineage information that is currently available in lakeFS but not exposed easily, and mimics the behavior of git blame

How

Given the lakeFS API already supports listing the log of commits for an object or prefix (🎉), this could be a `

We're using marshmallow to parse whylogs config from YAML

However, Pydantic is much more powerful as it allows users to set config via various mechanims, from YAML, JSON to Environment settings.

We should consider moving to pydantic

What type of re_data dbt macro you would like to add

• validate

What macro should be doing

Return true is string is a valid JSON and can be parsed to JSON

Motivation

As odd-platform supports redshift and so on, it would be awesome to support BigQuery integration.

What is the feature request? What problem does it solve?
We need to integrate some static code analysis in order to be able to better ensure code quality and security.

Suggested solution
In the current Github Org SonarCloud and/or Codecov are approved so we should use one (or both) of them.

Additional context
This also was found as a gap in the evaluation https://bestpracti