Upgrade from v2.1.2 to v2.6 producing 1051 new SQL DQD errors

[Ram-SN]

Hi,

As mentioned in a previous Q&A post, we have successfully updated the application from version v2.1.2 to v2.6. When the dqd_script.r was triggered we were notified of 1051 new SQL errors that we didnt previously see in the version 2.1.2. We noticed two different kinds of errors:

1. Unrecognized name:na at [19:70] (Level: Concept, Table
   : Measurement, Field: Measurement_concept_ID, Check: plausibleUnitConceptIds)
2. Failed to parse input string "1950-06-01" (Check: plausibleTemporalAfter)

Both of these seem to be parsing errors which did not arise in the previous version. We have not changed the source of tables (GBQ) when uprading to new version.

Any help/input into this matter is greatly appreciated, thanks!

[katy-sadowski]

Thanks for the report!

I see what the issue is in plausibleTemporalAfter and have filed this ticket to fix the bug: #549.

For plausibleUnitConceptIds - could you please share the full error report that shows the faulty SQL query?

Thank you :)

[Ram-SN]

Yes we are using a slightly modified version, so do you suggest we edit this concept_id in the concept level csv?

[katy-sadowski]

Yes - I'd make sure that if the plausibleUnitConceptIdsThreshold is populated, there are plausibleUnitConceptIds listed. I would also recommend following the lists of plausibleUnitConceptIds from the latest release as this check was overhauled for accuracy recently. Let me know if that works :)

[Ram-SN]

Hi, Im trying to downgrade to a previous version but the script to executeDQ seems to still be picking the plausibleTemporalAfter SQL query from v2.6. Made sure the package version is what i want.Is there something Im missing out?

[katy-sadowski]

It looks like this bug has been present since version 1.4! Maybe you previously had this check disabled?

[Ram-SN]

Yes we had to downgrade an even older version due to version mismatch on our end. Looking forward to the patch in the newest version to fix the plausibleTemporalAfter bug. When can we expect this? Thank you for the support!

[katy-sadowski]

I'm hoping to ship the fix with the next release in the next couple of weeks :)

[katy-sadowski]

The fix is merged into develop: #549

It'll be another week or so before this is released in a new version. I'll keep you posted!

[Ram-SN]

Hi Katy, following up on this, thanks!