You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
case class AnalysisBasedConstraint should have var errorMessage = s"Value: $assertOn met the constraint requirement!" because $assertOn value specifies the number of rows which met the requirement.
To Reproduce
Steps to reproduce the behavior:
Go to package com.amazon.deequ.constraints
Click on AnalysisBasedConstraint
Scroll down to pickValueAndAssert
See error on else part var errorMessage = s"Value: $assertOn does not met the constraint requirement!"
Expected behavior
var errorMessage = s"Value: $assertOn met the constraint requirement!"
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This value specifies the number of rows that met the requirements !
The text was updated successfully, but these errors were encountered:
There is no bug here.
Actually we are passing some threshold value there in assertion
Assertion is like
val assertion: Double => Boolean = {
_ >= 0.6
}
we pass this assertion in constraint
and finally it goes like this
assertOn = (number of row passed the constraint) / (total number of rows)
if(assertion(assertOn)) print Success
else print Value: $assertOn does not met the constraint requirement!"
Describe the bug
case class AnalysisBasedConstraint should have var errorMessage = s"Value: $assertOn met the constraint requirement!" because $assertOn value specifies the number of rows which met the requirement.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
var errorMessage = s"Value: $assertOn met the constraint requirement!"
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This value specifies the number of rows that met the requirements !
The text was updated successfully, but these errors were encountered: