Genserver.Utils.ForcedLoad (etl_core v0.1.4)
Module oriented to the instructions necessary to load data in a forced way
Link to this section Summary
Functions
Historical load. The information is queried from ElasticSearch.
Link to this section Functions
Link to this function
record_historical_load(business, type_documentary, queue, start_date, end_date, config_amqp, config_notification, config_error_notification, config_elastic, config_nodesearch, config_ticket)
Historical load. The information is queried from ElasticSearch.
parameters
Parameters:
- business: Atom. Business to which the process will be applied.
- type_documentary: String. Type of documentary with which to work.
- queue: String. Queue to which the records will be sent.
- start_date: Tuple. Lower limit date, to filter by the "inserted_at" field. Expected structure {{year, month, day}, {hour, minute, second}}, where each inner value is numeric.
- end_date: Tuple. Upper limit date, to filter by the "inserted_at" field. The structure matches the `start_date` field.
- config_amqp: List. Configuration to establish the connection with the AMQP queues.
- config_notification: {String, List, String}. Configuration for sending notifications. The order of the elements corresponds to: url, headers, environment.
- config_error_notification: {String, List, String}. Configuration for sending error notifications. The order of the elements corresponds to: url, headers, environment.
- config_elastic: {String, List}. Configuration for the use of the ElasticSearch service. The order corresponds to: url, headers.
- config_nodesearch: {String, List}. Configuration for the use of the NodeService service. The order corresponds to: url, headers.
- config_ticket: {String, List, String, String}. Configuration to obtain valid tickets. The order corresponds to: url, headers, username, password.