3 ms·
I used greenplum until about three years ago when that employer replaced it. There is no way to describe it other than brittle and unsuited for production work
by x0x0 11y ago
I used greenplum until about three years ago when that employer replaced it. There is no way to describe it other than brittle and unsuited for production work. My peers discovered multiple ways to kill the db, all with data loss. Before you use it you should find a current user. It is one of a handful of techs on my personal "never again" list.
Licensing was also ludicrously expensive, including an attempt to multiply our license cost by 10 one year. I'd be very leery of lock-in given the owners. I also suspect this is the result of a failed attempt to sell it and is an open-source hail mary.
- eis 11y agoI'm curious as to what the replacement was and if you were happy with it.
- x0x0 11y agoWe replaced gp with a combination of things. we ported dremel to our heavily customized hadoop (it is, even now, at least 10x more performant than the public hadoop code, drawing from experiences of running on 5k+ physical nodes, plus yahoo is where software engineering goes to die) we also ended up using spark while neither of the above is as convenient as greenplum could be, they also didn't have 2+day outages every other month while hundreds of tb of data had to be regenerated and reloaded for the reporting powered by greenplum. They also didn't cost millions of dollars a year that emc wanted. Overall, I think we were very happy ending gp.
- jacques_chester 11y ago> I'd be very leery of lock-in given the owners. The owner is now Pivotal (it used to belong to EMC). Almost all our product code is opensource. The culture comes from Pivotal Labs DNA, which is a resolutely opensource shop. > I also suspect this is the result of a failed attempt to sell it and is an open-source hail mary. It's not.