Can we set 100g? Or maybe 1000g? ... View more

Is ther any solution for this issue. I am facing same issue. Table is holding very huge data and while doing insert overwrite , files are getting placed in my user directory, /user/anjali/.Trash, causing hive action in oozie to fail after 1.5 hr long run. Please help. The table is external and ev even I changed it to internal table, auto purge = true is not working. ... View more

I have the same question too.. ... View more

Thanks for the information! ... View more

I didnt quite understand your statement..why does it matter if BDM has other execution engines like Blaze and spark?   Impala itself is another execution engine like spark and blaze, we dont need to use impala jdbc connection in BDM using spark and Blaze you can just use it in native mode. ... View more

" UTC timezone conversion issue going on with only Parquet backed tables." > how do Cloudera Customers deal with this issue? I fear the first solution is to have all your servers use the same (UTC) timezone. We also have this flag setconvert_legacy_hive_parquet_utc_timestamps=true and hope to get rid of it once we move everything to UTC. ... View more

Hello Jim, That seems to have been the problem. Although the krb5.conf files were effectively identical the two Cloudera Managers had been configured by specifying the KDC by name and by IP address. We now have BDR working between two different Cloudera Managers, but not between two clusters with the same Cloudera Manager. ... View more

@alexmc6   "*" is not a valid regex.  ".*" may be what you were going for...   I am not quite clear on your business requirement, but I think you are saying that you want to maybe create 10 replication schedules that will replicate chunks of 10 of your area databases... akin to this:   area([0-9]|1[0])_.*db     ... View more

Sorry to drag up an old topic but I am hoping there is now some official guidance from Cloudera - or perhaps a reference architecture.    As soon as an organisation builds a Cloudera EDH cluster in one Amazon AWS region (or Azure or Google Cloud, or whatever) then they soon realise they might want another cluster in a different region or a different Availability Zone.    Personally I am happy sticking with one Region but multiple AZs - so I am thinking that I want one Cloudera Director, one Cloudera Manager, and separate clusters in each AZ.  ... View more