Viktor Klang wrote: > Absolutely, perhaps I'm tainted by write-heavy systems and perhaps I'm > just failing to see the overhead we're talking about. > Perhaps I overlooked it, but the paper didn't mention performance for > small writes and potentially multiple nodespanning transactions. HadoopDB makes no claim to any support for writes at all, I'm just speculating that It Should Be Possible given my understanding of its architecture, which is admittedly limited and based solely on reading the paper and a bit of the code. :) > I'm inclined to believe that some sort of immutable records storage > would simlify the semantics (analytic queries are IMHO very seldom > demanding real-time snapshots) Analytical queries against static data are exactly what it's for. I have no experience with its competition, namely parallel/distributed column-oriented databases, so I can't say whether they're any happier with writes.
FYI I brought up HadoopDB on the NoSQL list too but so far not too many takers... -0xe1a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
