I hope this would be solved soon since it causes a lot of concern from 
administration perspective.

Also this issue can be a huge problem when you use Apache Ranger for 
authorization. Apache Ranger currently doesn’t support Hbase default 
namespace!! That means you can’t give users permission to default:* in ranger.

Anyone has faced this issue before?

Regards,
Mehrdad



From: Luke Han [mailto:[email protected]]
Sent: 2016, July, 19 11:08 AM
To: [email protected]
Subject: Re: How to Define namespace for HbaseTable

We should resume this JIRA to have namespace to be supported in future releases




Best Regards!
---------------------

Luke Han

On Tue, Jul 19, 2016 at 3:45 AM, Niasari, Mehrdad 
<[email protected]<mailto:[email protected]>> wrote:
I found this issue on the community:
https://issues.apache.org/jira/browse/KYLIN-224

But it seems there is no solution for it yet, is that right?


From: Niasari, Mehrdad 
[mailto:[email protected]<mailto:[email protected]>]
Sent: 2016, July, 18 2:59 PM
To: [email protected]<mailto:[email protected]>
Subject: How to Define namespace for HbaseTable

Hi community,

How can I get Kylin to create all Hbase Tables in a specific namespace in Hbase?

Just to make it clear, I have defined a namespace for kylin.metadata.url, but 
my question is not about metadata table, is about the actual HbaseTable.

Thanks,
Mehrdad



_______________________________________________________________________

If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.

_______________________________________________________________________

If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.

_______________________________________________________________________
If you received this email in error, please advise the sender (by return email 
or otherwise) immediately. You have consented to receive the attached 
electronically at the above-noted email address; please retain a copy of this 
confirmation for future reference.  

Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur 
immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté 
de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse 
courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation 
pour les fins de reference future.

Reply via email to