data-quality

Is your feature request related to a problem? Please describe.
Most of operations of GE are executed from CLI, which is not friendly to non-programmer.

Describe the solution you'd like
A management system with all kinds of web UI to create expectation, query validation results etc.

#306 adds static type checking; it would be nice to switch over to mypy strict mode (--strict) once we have full coverage with type annotations.

Is your feature request related to a problem? Please describe.
When creating a SQLite online store your only option is to create it on the filesystem. As every access needs to hit the filesystem then this slows down the online store.

Describe the solution you'd like
I'd like an option :memory: to use an in memory SQLite store instead. Eg in feature_store.yaml:

online

Many lakeFS users integrate it with Spark.
To simplify the search experience of docs, Spark integrations should be a top-level category in our documentation.

Description

The table headers in SummaryDriftReport are misaligned with the rest of the table, content, as shown below:

Suggestions

Table header should be aligned with content.

Related

Relates to organization/repo#number <!-- Reference related commits, issu

You might have a column called money in one database, and amount in another. Today we don't have a way to have the columns have different names across the two databases. In the Python API, perhaps it's sufficient to just make it based on the position in the column tuple.

For the CLI, maybe we could use: -c amount:money.

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

Currently Feathr only supports getting a single type of keys thru client.get_online_features or client.multi_get_online_features. Essentially they are just sending the HMGET commands to Redis, say for "product_id".

Per this discussion (https://feathrai.slack.com/archives/C036HEUQM08/p1658237223861509), it would be good to add a convenient API to get multiple type of keys, say get some "prod

Specification must have an order parameter for fields. ODD Platform must take it into account after it's implemented on the ODD Spec side