Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Our ETL process is heavily monitored so we never miss a days data, but we got a surprising error "cant build aggregates - missing data, aborting MV refresh, data will be a day old". It was the year to date (YTD) calculation - no data for 29/2/2023 to compare to today.


This is why -365 days can be better than -1y.


Until tomorrow when your system is now off by a day for the next 365 days.


Frankly unless you've considered it ahead of time and thought you'd handled it, IMO you want the error. What's the correct thing to do here? I don't think it's necessarily -365d, it might be, but if I was GP I'd be glad for the chance to consider it and decide what's correct - instead of it just blowing up or even worse silently going whichever way's wrong and undetected for a while.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: