After adding v2 standard column support to ndt5 parser and ndt5 configuration to v2 gardener with changes to recognize ndt5, data is parsed into the tmp_ndt dataset tables but not copied to raw_ndt, though gardener does not seem to report errors.
Evidence of data in tmp tables
select date, COUNT(*) from `mlab-sandbox.tmp_ndt.ndt5` where date > date('2019-01-01') group by date order by date
The gardener logs include all steps, load, copy, delete, but they do not appear to take effect. The "deleted" tmp date partition is still present in the query above. The "load" and "dedup" steps appear to take 20-30sec, but the "copy" step is only 100ms, suggesting that it is not actually being performed. (these values are representative of other dates).
After adding v2 standard column support to ndt5 parser and ndt5 configuration to v2 gardener with changes to recognize ndt5, data is parsed into the
tmp_ndt
dataset tables but not copied toraw_ndt
, though gardener does not seem to report errors.Evidence of data in tmp tables
The gardener logs include all steps, load, copy, delete, but they do not appear to take effect. The "deleted" tmp date partition is still present in the query above. The "load" and "dedup" steps appear to take 20-30sec, but the "copy" step is only 100ms, suggesting that it is not actually being performed. (these values are representative of other dates).
Why is data not reaching the
raw_ndt.ndt5
table?Logs from gardener for a recent date: