-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comp-fields exception when all columns in primary key #1309
Comments
Hi, I believe there is a user misunderstanding here - though DVT's error message could be better. Our documentation says DVT can detect this condition and throw an error message and return a non zero exit status - rather than printing the confusing Sundar Mudupalli |
I still think we should be able to complete the validation, or are we just saying they need to use concat or hash instead? I did have a look at this myself today and my suggestion of dealing with it in the combiner is really difficult. I haven't often looked at that code before and it's hard to understand. However I revisited your original suggestion of adding a placeholder value to the validation. I couldn't see how to push a literal through but could see how to use one of the primary key columns to do the same job. I created a branch and pushed an exploratory commit for discussion purposes. I'm not wedded to this idea, just thought it was worth sharing/discussing. |
I am not clear about the expected result. I used two simple tables
and then issued the DVT command
|
We can park this for now and I'll ask the customer what they would expect to see. For completeness here is output for the experimental commit on the feature branch:
But it's just a bit of a hack. So better to pause than rush a hack though. |
Test case:
The text was updated successfully, but these errors were encountered: