RE: export/import in hive failing with nested directory exception!

2015-11-13 Thread Mich Talebzadeh
nt: 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> &

Re: export/import in hive failing with nested directory exception!

2015-11-12 Thread Gopal Vijayaraghavan
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

Re: export/import in hive failing with nested directory exception!

2015-11-12 Thread Gopal Vijayaraghavan
> I am doing a simple export and import test from one database in Hive to >another database in the same Hive instance. I thought this would have >been straight forward. Not if ACID transactions are involved. > Copying file:

RE: export/import in hive failing with nested directory exception!

2015-11-12 Thread Mich Talebzadeh
, therefore neither Peridale Ltd, its subsidiaries nor their employees accept any responsibility. -Original Message- From: Gopal Vijayaraghavan [mailto:go...@hortonworks.com] On Behalf Of Gopal Vijayaraghavan Sent: 13 November 2015 00:17 To: user@hive.apache.org Subject: Re: export/import in hive

Re: export/import in hive failing with nested directory exception!

2015-11-12 Thread Lefty Leverenz
This needs to be documented here: Limitations in the Hive Transactions wikidoc. -- Lefty On Fri, Nov 13, 2015 at 12:39 AM, sreebalineni . wrote: > Hello Gopal, > Are there

Re: export/import in hive failing with nested directory exception!

2015-11-12 Thread sreebalineni .
Hello Gopal, Are there any plans for fixing this? Any idea? On Fri, Nov 13, 2015 at 6:31 AM, Gopal Vijayaraghavan wrote: > Hi, > > >Thanks Gopal. Indeed table t is defined as ORC and transactional. > > > >Any reason why this should not work for transactional tables? > > The