Re:Machine Learning Engineer Guide: Feature Store vs. Data W...
by freewilly1040 on Thursday October 08, 2020 @12:57PM
(#24721099)
> we can still get signal out of it
Today you can, but then when the app owner drops a column (or worse, stop populating it!) in a month that signal will break, and the data lake maintainer will be in the unenviable position of navigating the completely undocumented dependency.
Re:Machine Learning Engineer Guide: Feature Store vs. Data W...
by dmpetrov on Thursday October 08, 2020 @05:50PM
(#24724292)
That's might be fine. Anyway, you need to retrain your models quite often due to the concept drift. Solving data problems like this is just a part of model retraining (and concept drift).
Re:Machine Learning Engineer Guide: Feature Store vs. Data W...
by zekrioca on Thursday October 08, 2020 @10:49AM
(#24719558)
More or less how a proof-of-concept for new type of wine turns out to be sold as Champagne..
Re:Machine Learning Engineer Guide: Feature Store vs. Data W...
by loopz on Thursday October 08, 2020 @11:33AM
(#24720078)
As another poster said, if it's the raw data, the raw deal, it's the bets source and nice to have (but could become expensive, so better it is paid for in scale).
If it's something else, it's the antithesis of data science.
That's kind of what I understand as well, but the data science folks pitched it in a slightly more positive way, like, "Please don't limit us just to the data you have time to nicely structure and validate. We want all of it. It doesn't matter if a column is getting truncated to three characters or columns are mislabeled or there are amounts in dollars and euros mixed together; we can still get signal out of it."