Skip to content

Conversation

@ankurjuneja
Copy link
Contributor

@ankurjuneja ankurjuneja commented Oct 19, 2021

Rationale

It is hard to determine the value of date that does not get normalized during ETLs. This change logs such values which are of type other than string and date.

else {
if (val['getTime']){
normalizedVal = new Date(val.getTime());
console.log('EHR trigger script is being passed a date with value: ' + val);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will log to the console (an improvement over the current behavior) and then fail the job with the same unhelpful error message.

I've asked Matthew to share the full log file. I checked the recording but he didn't scroll down quite far enough to show the root exception during the screensharing yesterday.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will give us the value of the date which we were eyeballing in granite and couldn't find.

@labkey-jeckels
Copy link
Contributor

Does the platform PR effectively make this logging redundant?

@ankurjuneja
Copy link
Contributor Author

I think this PR will be useful for looking into the failures of locations ETL, the platform PR will log the error messages for arrivals ETL.

@ankurjuneja ankurjuneja merged commit cf55aa4 into release21.7-SNAPSHOT Nov 5, 2021
@ankurjuneja ankurjuneja deleted the 21.7_fb_logNormalizingDate branch November 5, 2021 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants