[Feature] updating code to work for retries if the save table fails

[asingamaneni]

Description

Making code changes so as to support retries for writing into table if it fails. Update table properties only if the property is not already written.

Related Issue

60

Motivation and Context

When there are multiple processes writing at the same time into the stats table, having issues with concurrent writes. Adding retries and also write table properties only when not written.

How Has This Been Tested?

The code has been unit tested

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5e6c601) 100.00% compared to head (f4e5876) 100.00%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #61 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 22 22 Lines 1441 1447 +6 ========================================= + Hits 1441 1447 +6 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[Umeshsp22]

LGTM

[phanikumarvemuri]

I see we are retrying the write irrespective of exception caused. Should we not retry only when it failed for concurrent writes ? Also as per delta Lake doc multiple Inserts should not conflict. Can you please share the exception details ( the stack trace ) ?