"I am still exploring how to get external DB done on hive, oozie and those monitoring DB "   Can you please elborate more sorry , I can certainly give you more information. ... View more

hi! where could I find the new syllabus materials (vm and pdfs) ??? I have pending my exam since january... thanks in advance. ... View more

@bdgreek   I tried the below queries and it shows the column as created (Sales$). Not sure it is due to your version     create table mydb.test1 (`Sales$` float) describe formatted mydb.test1 describe mydb.test1     ... View more

My bad, that was the only thing i didn't try lol. BTW, this is the solution. Thanks ... View more

It is an internal table. The creation process was using the HUE GUI to 'Create a new table manually' in the Metastore Manager for the Hive default database. I didn't choose the 'Create a new table from a file' option, which allows a user to specify if it should be an external table.    I updated my reply to saranvisa's use cases, and the underlying HDFS files were deleted only if the HUE user who dropped the table was its creator.   Fortunately, I do have access to HDFS superuser via the command line and was able to delete the table from my prior incident. Thanks for providing an alternative in the event that is not the case, especially since when deployed most users won't have command line access let alone HDFS superuser. Sounds like the trade-off is ease of use vs. level of security. ... View more

Thanks a lot for the above steps, i really was wondering how i should install different version of connector.. I'll soon follow the steps and inform the results. 🙂 ... View more

That is a fair question of what is 'appropriate'. I was hoping there would be an option to select a default behavior to do so. For example, upon 'usr1' creating an index, the following permission would be generated:   collection='the_new_idx"->user=usr1->action=*   I imagine other global default behaviors could exist such that the auto-generated permission sets access for new collections at a role level instead of user level.  ... View more

On the Impala dev team we do plenty of testing on machines with 16GB-32GB RAM (e.g. my development machine has 32GB RAM).  So Impala definitely works with that amount of memory.   It's just that with that amount of memory it's not too hard to run into capacity problems if you have a reasonable number of concurrent queries with larger data sizes or more complex queries.   It sounds like maybe the smaller memory instances work well for your workload. ... View more