My question is a "what if" question, not a production issue. It seems natural, when replacing traditional database with hive, to ask how much robustness is sacrificed for scalability. My concern is that if a file is partially loaded, there might not be an easy way to clean up the already loaded data before re-loading the data. The lack of unique index also does not make it easy to avoid duplicate data either, although duplicated data can perhaps be deleted after the load.
On Mon, Jun 13, 2011 at 7:12 PM, Martin Konicek <martin.koni...@gmail.com>wrote: > Hi, > > I think this is a problem with open source in general and sometimes it can > be very frustrating. > However, your question is more of a "what if" question - you're not in the > trouble of finding a horrible bug after you deployed to production, am I > right? > > Regarding your question, I would guess that if LOAD DATA INPATH crashes > while moving files into the Hive warehouse, the data which was moved will > appear as legitimate loaded data. Or the files will be moved but the > metadata will not be updated. In any case, you should detect the crash and > redo the operation. The easiest answer might actually be to look into the > source code - sometimes it can be easier to find than one would expect. > > Not a complete answer, but hope this helps a bit. > > Martin > > > On 14/06/2011 00:47, W S Chung wrote: > >> I submit a question like this before, but somehow that question is never >> delivered. I can even find my question in google. Since I cannot find any >> admin e-mail/feedback form on the hive website that I can ask why the last >> question is not delivered. There is not much option other than to post the >> question again and hope that the question get through this time. Sorry for >> the double posting if you have seen my last e-mail. >> >> What is the behaviour if a client of hive crashes in the middle of >> running a "load data inpath" for either a local file or a file on HDFS? Will >> the file be partially loaded in the db? Thanks. >> >> >>
