Distininguish between lead_preprocessed_data and historical_preprocessed_data #234
Labels
refactoring
Improvement to code structure that leaves functionalities untouched
Milestone
There is an issue in naming between
lead_preprocessed_data
andhistorical_preprocessed_data
. We must distinguish between both. Currently the code only names the output aspreprocessed_data
without any distinction.Acceptance Criteria
lead_preprocessed_data
for predictionAll the previous should work with both DB types: Local and S3
The text was updated successfully, but these errors were encountered: