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
Problem:
A conformity check is building two separate lists, consisting of the valid and invalid records, with a max total sum of the length of the input, which is becoming prohibitively slower after ~30 thousand records.
This holds true for a validation check, as under the hood it performs a conformity check and matches the result.
Proposal:
Optimise the validation check to not keep temporary results, while replicating the conformity check patterns. As an extra bonus (for multiple checks performed under a single validation) the validation stops once any check fails.
The text was updated successfully, but these errors were encountered:
gesta
linked a pull request
Apr 9, 2020
that will
close
this issue
Problem:
A conformity check is building two separate lists, consisting of the valid and invalid records, with a max total sum of the length of the input, which is becoming prohibitively slower after ~30 thousand records.
This holds true for a validation check, as under the hood it performs a conformity check and matches the result.
Proposal:
Optimise the validation check to not keep temporary results, while replicating the conformity check patterns. As an extra bonus (for multiple checks performed under a single validation) the validation stops once any check fails.
The text was updated successfully, but these errors were encountered: