Hey John, I have a secure cluster and some parquet files, I'll try this out
and report back.

On Monday, November 9, 2015, John Omernik <[email protected]> wrote:

> Has anyone been able to try/test this? I am curious if it's me only issue
> or something more of bug so I can open a JIRA if needed.
>
> John
>
> On Fri, Nov 6, 2015 at 11:06 AM, John Omernik <[email protected]
> <javascript:;>> wrote:
>
> > If someone has authorization/authentication setup, to reproduce:
> >
> > Have a Parquet table with directories underneath the main (I have
> > directories per day)
> >
> > Then issue REFRESH TABLE METADATA on the root of the table running an
> > authenticated user other than the drill bit user. (I am using mapr, I
> used
> > my user to run the query, and yes I have access to the data)
> >
> > Then run a normal query and see what the result is. .
> >
> > John
> >
> > On Fri, Nov 6, 2015 at 10:22 AM, Neeraja Rentachintala <
> > [email protected] <javascript:;>> wrote:
> >
> >> This doesn't make sense and seems like a bug.
> >> I think the right behavior is for the Drillbit to access the cache as
> >> Drillbit user at the query time (there is no user level metadata cache
> in
> >> Drill at this point).
> >>
> >>
> >>
> >> On Fri, Nov 6, 2015 at 6:57 AM, John Omernik <[email protected]
> <javascript:;>> wrote:
> >>
> >> > I ran REFRESH TABLE METADATA on a table, it completed successfully.
> >> >
> >> > When I tried a subsequent query, I get a IOException: Permission
> Denied
> >> on
> >> > .drill.parquet_metadata.
> >> >
> >> > I am running drill with authentication.  I ran the REFRESH TABLE
> >> METADATA
> >> > as user X, it appears the .drill.parquet_metadata was created and
> owned
> >> by
> >> > the user the drill bits are running as as is created with -rwxr-x-r-x
> >> >
> >> > My question is this: So, I can see why the file is owned by the drill
> >> bit
> >> > user, and the file is created with all can read permissions, but why
> am
> >> I
> >> > getting a permission denied when user X is trying to run a query?
> >> >
> >>
> >
> >
>

Reply via email to