Add CDM Timeseries Upload Queue

[devendra-lohar]

Add CDM Timeseries Upload Queue support for Timeseries Destination in DB Extractor.

[codecov]

Codecov Report

Attention: Patch coverage is 86.32479% with 16 lines in your changes missing coverage. Please review.

Project coverage is 77.99%. Comparing base (614939f) to head (f024e28).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
cognite/extractorutils/uploader/time_series.py	86.53%	14 Missing ⚠️
cognite/extractorutils/uploader_extractor.py	75.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #439      +/-   ##
==========================================
+ Coverage   77.71%   77.99%   +0.27%     
==========================================
  Files          42       42              
  Lines        3523     3613      +90     
==========================================
+ Hits         2738     2818      +80     
- Misses        785      795      +10     

Files with missing lines	Coverage Δ
cognite/extractorutils/uploader/__init__.py	100.00% <ø> (ø)
cognite/extractorutils/uploader_types.py	95.83% <100.00%> (+1.09%)	⬆️
cognite/extractorutils/uploader_extractor.py	79.16% <75.00%> (-1.14%)	⬇️
cognite/extractorutils/uploader/time_series.py	76.54% <86.53%> (+4.29%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mathialo]

The generic approach is pretty nice!

Noe more nitpick, but this is shaping up quite well

[mathialo]

Looks good to me!

[rsjr]

Looks good. However, I suggest adding two more integration test cases:

• A test case ingesting datapoints with status codes (similar to this)
• A non-happy path test case just to cover the behavior when ingesting datapoints with wrong type to an existing time series: the time series is numeric but you try to ingest string datapoints (or vice-versa).

[rsjr]

This fix you added here 8e63e36

This doesn't look to be related to the changes in this PR? Is it fixing some other side effect from somewhere else?

[devendra-lohar]

This fix you added here 8e63e36

This doesn't look to be related to the changes in this PR? Is it fixing some other side effect from somewhere else?

@rsjr
Yes this does not directly relate to the current PR but rather is inline with the latest release on cognite-sdk and fixing the resulting mypy error being caused.

[rsjr]

risk review ok