Hi Gautam,
Thanks for response !! I have filed a jira for this @ https://issues.apache.org/jira/browse/RANGER-219 Also I would like to discuss about one other scenario of hive policy: If we have specified 2 databases, for example: default, test & one table name e.g. customer then in database, resources are stored as: "default/customer, test/customer". But customer table belongs only to default database so how this type of scenario("customer" table is not in "test" database but we have stored resource pattern "test/customer") is handled? ------- Thanks & Regards, Hanish Bansal Software Engineer, iLabs Impetus Infotech Pvt. Ltd. (O) : +91.120.4092200-2790 (M) : +91.9953399925 ________________________________ From: Gautam Borad <[email protected]> Sent: Friday, January 16, 2015 8:11 PM To: [email protected] Subject: Re: Autocomplete behavior of hive tables/columns Hi Hanish, Yes, that is the expected behavior in current implementation. If there are multiple values in database/tables, the autocomplete for dependent field will not work. We can raise a Jira to discuss how to handle such scenarios and provide better functionality to users. Thanks. On Fri, Jan 16, 2015 at 12:55 PM, Hanish Bansal <[email protected]<mailto:[email protected]>> wrote: Hi All, When defining the policy for hive resource, autocomplete for hive tables and columns is not working properly. If multiple databases are specified in database name then autocomplete for table is showing tables only for first database. Similar is in case of columns, if multiple tables are specified in table name then autocomplete for column is showing columns only for first table. Please let me know the expected behavior. -- Thanks & Regards Hanish Bansal -- Regards, Gautam. ________________________________ NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
