awslabs / awslabs/deequ

Numeric value in constraint_message column should be accessible in its own column

Open
#360 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Scala
Stars
3.6k
Forks
586
Avg merge
13d 13h
Merged PRs (30d)
1

Description

For constraints_verification_results we want access to the measured value of the constraint itself. Presently this only appears accessible within the constraint message column.

There should be a separate column, constraint_value, that contains this value.

![Screen Shot 2021-04-27 at 12 04 52 PM](https://user-images.githubusercontent.com/29832552/116275170-5da1b380-a751-11eb-86d7-284720a1d5f3.png)

Contributor guide

Open the contributing guide

Research direction

Locate where constraints_verification_results and constraint_message are produced, then inspect the related schema and tests. Confirm how the measured value is extracted and exposed as constraint_value; done means the separate column is populated and covered by tests without losing the existing message.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala, spark
Domain
data-engineering, testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.