I'm loocking by best practices for architecture and naming hdfs file path names for naming taxonomy  considering the user are analytical users who implement data preparation and data modeling process?   I appreciate to share tips to desing a service on HDFS with overwrite strategy enough to get easy and friendly data model for train analytical and statistical models process in an modeling as a service.   For instance to get files with +3000 columns and storage more than 48 months of history. any tip to manage huge volumen of data.     ... View more

I'm loocking by best practices for architecture and naming hdfs considering the user are analytical users who implement data preparation and data modeling process?   I appreciate to share tips to desing a service on HDFS with overwrite strategy enough to get easy and friendly data model for train analytical and statistical models process in an modeling as a service.   For instance to get files with +3000 columns and storage more than 48 months of history. any tip to manage huge volumen of data.     ... View more

I'm loocking by best practices for architecture and naming hdfs file path names for naming taxonomy  considering the user are analytical users who implement data preparation and data modeling process?   I appreciate to share tips to desing a service on HDFS with overwrite strategy enough to get easy and friendly data model for train analytical and statistical models process in an modeling as a service.   For instance to get files with +3000 columns and storage more than 48 months of history. any tip to manage huge volumen of data.     ... View more