awslabs / awslabs/deequ

Improve CategoricalRangeRule in constraint suggestion

Open
#65 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Scala
Stars
3.6k
Forks
586
Avg merge
13d 13h
Merged PRs (30d)
1

Description

When running constraint suggestion for CategoricalRangeRule for columns with cardinality of a few dozens, the suggested constraint is failing by a very small margin (Value: 0.99999907 does not meet the constraint requirement!).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate CategoricalRangeRule and the constraint-suggestion code, then reproduce the failure with a column whose cardinality is a few dozen. Check how the suggested constraint compares the value near 1.0, and add a regression test for the reported precision margin. Done means the suggested constraint no longer fails at values such as 0.99999907.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala, spark
Domain
data, testing
Issue type
Bug
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.