Fix Error processing Generic_Case,LDF_GENERIC data in nedss-datareporting-post-processing-service#724
Open
Fix Error processing Generic_Case,LDF_GENERIC data in nedss-datareporting-post-processing-service#724
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The original ticket reported that LDF data was not flowing into
RDB_Modern.LDF_DATAandRDB_Modern.LDF_DATAMART_COLUMN_REFtables, with steps to reproduce.After multiple attempts following the steps referenced, I could not replicate this error. However while testing, I encountered a different PostProcessingService error:
Error processing Generic_Case,LDF_GENERIC data with ids '10009310': DataProcessingExceptionThe error logged in
job_flow_logwas: Column names in each table must be unique. Column nameDATAMART_COLUMN_NMin table#TMP_ALL_GENERICis specified more than once. That happened because#TMP_ALL_GENERICwas built fromA.\*plusB.DATAMART_COLUMN_NMunder the same name. this is now explicitly set.There was also an older secondary defect in the same procedure: the nulling step could call SUBSTRING on an empty string and it was hardcoded to
LDF_GENERICinstead of using the target table parameter. These were both corrected.Related Issue
APP-420: LDF processing failure
Additional Notes
Ignore whitespace changes when reviewing changes; there were a lot of trailing whitespace which does not get cleaned up automatically in the repo.
Checklist
I have updated the documentation, if applicable.I have added or updated test cases to cover my changes, if applicable.