This potentially breaks the ACID properties of Hive.
My own take is that export/import functionality was added before ACID properties and transactional tables were added to Hive and as such did not cater for this type of work. There are two options IMO: 1. Update documentation for import/export to highlight the limitations with regard to transactional tables 2. Provide an alternative mechanism on how to migrate transactional tables. HTH, Mich Talebzadeh Sybase ASE 15 Gold Medal Award 2008 A Winning Strategy: Running the most Critical Financial Data on ASE 15 http://login.sybase.com/files/Product_Overviews/ASE-Winning-Strategy-091908.pdf Author of the books "A Practitioner’s Guide to Upgrading to Sybase ASE 15", ISBN 978-0-9563693-0-7. co-author "Sybase Transact SQL Guidelines Best Practices", ISBN 978-0-9759693-0-4 Publications due shortly: Complex Event Processing in Heterogeneous Environments, ISBN: 978-0-9563693-3-8 Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume one out shortly http://talebzadehmich.wordpress.com <http://talebzadehmich.wordpress.com/> NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be understood as given or endorsed by Peridale Technology Ltd, its subsidiaries or their employees, unless expressly so stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility. From: sreebalineni . [mailto:sreebalin...@gmail.com] Sent: 13 November 2015 05:39 To: user@hive.apache.org Subject: Re: export/import in hive failing with nested directory exception! Hello Gopal, Are there any plans for fixing this? Any idea? On Fri, Nov 13, 2015 at 6:31 AM, Gopal Vijayaraghavan <gop...@apache.org <mailto:gop...@apache.org> > wrote: Hi, >Thanks Gopal. Indeed table t is defined as ORC and transactional. > >Any reason why this should not work for transactional tables? The committed transactions list is actually missing from the exported metadata. So the EXPORT as it exists today is a dirty read snapshot, which is not a good thing when the data is continously being streamed in. I don't think IMPORT likes that (and why should it?). Try with a fully compacted table. Cheers, Gopal
