News for hackers. Stuff that matters.
Re:How to make MongoDB not suck for analytics by dizzystar on Sunday July 01, 2018 @09:07PM (#17438676)
Except that devs have to do ETL every day so analysts can do their query work.
Re:How to make MongoDB not suck for analytics by marcinzm on Sunday July 01, 2018 @09:23PM (#17438728)
Which you'll likely want with any DB since analytics workloads are very different than the usual production DB workloads.
Re:How to make MongoDB not suck for analytics by twblalock on Sunday July 01, 2018 @09:23PM (#17438725)
That can be automated.
Re:How to make MongoDB not suck for analytics by dizzystar on Sunday July 01, 2018 @10:55PM (#17439043)
In theory, yes; in practice, not really.
Re:How to make MongoDB not suck for analytics by sdoering on Monday July 02, 2018 @12:49AM (#17439399)
I tend to disagree. Having multiple automated ETL processes running for different projects/clients/colleagues I see that the code does not change as often, as I had anticipated.

Automation here (in my case) is a net win on time.

Re:How to make MongoDB not suck for analytics by marcinzm on Monday July 02, 2018 @09:07AM (#17441285)
Why? Technically speaking, simple ETL is easy to automate and not too much maintenance headache.