Added logs for not found records
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [YES]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Added logs for not found
records: due to missed metadata, missed during read from cloud storage and missded during conversion.
Some records were missed during indexing process
Edited by Dmitrii Novikov (EPAM)
Merge request reports
Activity
changed milestone to %M17 - Release 0.20
added Common Code label
requested review from @Stanislav_Riabokon and @Rustam_Lotsmanenko
assigned to @Dmitrii_Novikov
added MREnhancement label
added 6 commits
-
20834938...65ef04a9 - 5 commits from branch
master
- b0948e52 - Merge remote-tracking branch 'origin/master' into add-logs
-
20834938...65ef04a9 - 5 commits from branch
mentioned in commit 2e3a7d89
mentioned in commit 9a2a78f0
Please register or sign in to reply