issue #757 Initialization failure handling control

[wajda]

fixes #757

Adds a new config property:

spline.onInitFailure = LOG | BREAK

• LOG - log the error and carry on with Spark job (default behavior)
• BREAK - propagate the error to the calling Spark process.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[github-actions[bot]]

JaCoCo code coverage report

File	Coverage [40.56%]	:x:
AgentConfig.scala	84.38%	:green_apple:
AgentBOM.scala	72.85%	:x:
InitFailureHandlingMode.java	0%	:x:
SparkLineageInitializer.scala	0%	:x:

Total Project Coverage	42.08%	:green_apple:

[cerveada]

As I understand it there are three places from which agent code is run:

• Programmatic init
• codeless init
• Spark listener

Spark listener is wrapped in try catch, so we can't influence what is happening outside of that. For both init methods are you sure there is no catch block that will make this config unusable?

[cerveada]

Can we have tests for this?