Why not support multiple job error handlers?

[TeslaCN]

Feature Request

shardingsphere-elasticjob/elasticjob-api/src/main/java/org/apache/shardingsphere/elasticjob/api/JobConfiguration.java

Lines 64 to 68 in e1bf862

	private final String jobErrorHandlerType;
	private final Collection<String> jobListenerTypes;
	private final Collection<JobExtraConfiguration> extraConfigurations;

Describe the feature you would like.

Remove field "jobErrorHandlerType". The job will have 3 error handlerse if I add 3 instances of ErrorHandlerConfiguration.

[terrymanu]

It is better to support multiple job error handlers.
I am not sure we can do it now or after 3.0.0-beta release.

[TeslaCN]

Current API

    private JobConfiguration createJobConfiguration() {
        return JobConfiguration.newBuilder("test_job", 3)
                .cron("0/1 * * * * ?").shardingItemParameters("0=A,1=B,2=C").jobParameter("param").failover(true).misfire(false)
                .jobErrorHandlerType("THROW")
                .description("desc").build();
    }

How about the following API ?

    private JobConfiguration createJobConfiguration() {
        return JobConfiguration.newBuilder("test_job", 3)
                .cron("0/1 * * * * ?").shardingItemParameters("0=A,1=B,2=C").jobParameter("param").failover(true).misfire(false)
                .addExtraConfigurations(new EmailConfiguration())
                .addExtraConfigurations(new DingtalkConfiguration())
                .addExtraConfigurations(new LogErrorHandlerConfiguration())
                .description("desc").build();
    }

[terrymanu]

The configuration of THROW error handler maybe need to discuss.
It is in consist with type based config like sharding or executors

[TeslaCN]

How to config THROW error handler in the new API?

THROW is specified by a configuration class without any fields.

public final class ThrowErrorHandlerConfiguration implements ErrorHandlerConfiguration {
    
    @Override
    public String getType() {
        return "THROW";
    }
}

I can send a email before throw an exception.

                .addExtraConfigurations(new EmailConfiguration())
                .addExtraConfigurations(new ThrowErrorHandlerConfiguration())
                .addExtraConfigurations(new LogErrorHandlerConfiguration()) // Will not be invoked.

[TeslaCN]

I did some changes in https://github.com/TeslaCN/shardingsphere-elasticjob/tree/fixes-1622

[terrymanu]

It is a good idea, maybe you can submit the pull request and we can review your change.

[TeslaCN]

The branch TeslaCN/fix-1622 is base on configuring job error handler by JobExtraConfiguration. Since #1626 has already revert the way to configure job error handler, I think we can further discuss this issue and do this in a future version.