ETL extensions - Atoti Hub

This section explains how ETL extensions can be made within Atoti FRTB. For these extensions, the Datastore Helper and Data Load Controller are used.

Organizing customizations

Extracting customizations into their own configuration class helps keep things tidy and aids in migration efforts when upgrading to a newer version of Atoti FRTB. Customizations can be placed into Configuration classes that are ensured to be picked up by the application. Example datastore customization:

@Configuration
public static class ClientCustomisations {

	@Bean(name = "Custom")
	@Order(DatastoreCustomisationSpringBeanOrder.PROJECT)
	public DatastoreConfiguratorConsumer addFieldCustomization(){
		return datastoreConfigurator -> datastoreConfigurator
				.appendField("ExistingStore", new CustomField("MyNewField", ILiteralType.STRING));
	}
}

Customizations are applied in a defined order, so every DatastoreConfiguratorConsumer bean must declare an @Order value. A project customization declares DatastoreCustomisationSpringBeanOrder.PROJECT, which is 100. For the other values and the rules that govern them, see What determines the order of datastore customizations?.

Include in FrtbApplicationConfig

For the customizations to be picked up, all added Spring @Configuration classes must be included in FrtbApplicationConfig located in /frtb-application/src/main/java/com/activeviam/frtb/application/config/.