Replies: 3 comments
-
Thank you for your kind feedback :)
To achieve max performance the checks are implemented as column expressions that expect a single dataframe. It is currently allowed to apply one dataframe for row level checks. If you want to perform joins or aggregations as part of the checks you could create the transformation before and apply checks on the result: Example:
Would this work for you? We will be working on ability to use multiple dataframes with a focus to compare them: We will also be soon adding ability to define data set level checks (aggregation level checks applied on the whole dataframe and not individual rows only): |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
This is now available with |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team:
First of aLL congratulations for the DQX Framework. is awesome to work with this
Suggestion regarding SQL_EXPRESSION. It would be very convenient if in this type of clauses you could do things like check a field within another table with filters or the ability to execute joins to bring the content of fields. I am currently translating rules that we have in an internal Data Quality engine and the sentences are like these: MaterialId in (SELECT DISTINCT Field A FROM .
WHERE somefield= 'X'). When parsing the JSON string I receive the message Invalid JSON: Expecting ',' delimiter: line 92 column 120 (char 2567)Beta Was this translation helpful? Give feedback.
All reactions