Hi Dimitris,
Here's a listing from my machine after I ran "./buildall.sh
-start_minicluster -start_impala_cluster -format -testdata -notests".
-- Philip
$sudo -u postgres psql
psql (9.5.12)
Type "help" for help.
postgres=# \c sentry_policy
You are now connected to database "sentry_policy" as user "postgres".
sentry_policy=# select * from "SENTRY_ROLE";
ROLE_ID | CREATE_TIME | ROLE_NAME
---------+-------------+-----------
(0 rows)
sentry_policy=# select * from "SENTRY_VERSION";
VER_ID | SCHEMA_VERSION | VERSION_COMMENT
--------+----------------+-------------------------------
1 | 2.0.0 | Schema version set implicitly
(1 row)
sentry_policy=# select * from "SENTRY_USER";
USER_ID | CREATE_TIME | USER_NAME
---------+-------------+-----------
(0 rows)
sentry_policy=# \dt
List of relations
Schema | Name | Type | Owner
--------+------------------------------+-------+----------
public | AUTHZ_PATH | table | hiveuser
public | AUTHZ_PATHS_MAPPING | table | hiveuser
public | AUTHZ_PATHS_SNAPSHOT_ID | table | hiveuser
public | SENTRY_DB_PRIVILEGE | table | hiveuser
public | SENTRY_GM_PRIVILEGE | table | hiveuser
public | SENTRY_GROUP | table | hiveuser
public | SENTRY_HMS_NOTIFICATION_ID | table | hiveuser
public | SENTRY_PATH_CHANGE | table | hiveuser
public | SENTRY_PERM_CHANGE | table | hiveuser
public | SENTRY_ROLE | table | hiveuser
public | SENTRY_ROLE_DB_PRIVILEGE_MAP | table | hiveuser
public | SENTRY_ROLE_GM_PRIVILEGE_MAP | table | hiveuser
public | SENTRY_ROLE_GROUP_MAP | table | hiveuser
public | SENTRY_ROLE_USER_MAP | table | hiveuser
public | SENTRY_USER | table | hiveuser
public | SENTRY_VERSION | table | hiveuser
public | SEQUENCE_TABLE | table | hiveuser
(17 rows)
On Thu, Mar 29, 2018 at 10:08 PM, Dimitris Tsirogiannis <
[email protected]> wrote:
> I enabled full logging in my postgres that hosts the sentry and metastore
> db and I don't see the table being created. If anyone has gone through the
> process, can you: a) verify that relation SENTRY_ROLE exists in your
> sentry_policy db, and b) tell me how many relations are in your policy_db.
>
> Thanks
> Dimitris
>
> On Thu, Mar 29, 2018 at 9:32 PM, Dimitris Tsirogiannis <
> [email protected]> wrote:
>
> > Good point. I used -format that in theory handles both the metastore and
> > the sentry policy dB. The sentry_policy db is created and has some tables
> > but not the SENTRY_ROLE.
> >
> > Dimitris
> >
> > On Thu, Mar 29, 2018 at 6:29 PM Jim Apple <[email protected]> wrote:
> >
> >> I think I might have once fixed that using
> >>
> >> ./buildall.sh -notests -format_metastore -format_sentry_policy_db
> >>
> >>
> >> On Thu, Mar 29, 2018 at 6:15 PM, Dimitris Tsirogiannis <
> >> [email protected]> wrote:
> >>
> >> > I tried rebuilding my minicluster but Sentry refuses to start. I get
> >> > "ERROR: relation "SENTRY_ROLE" does not exist in the sentry logs. Does
> >> that
> >> > ring any bells?
> >> >
> >> > Thanks
> >> > Dimitris
> >> >
> >> > On Tue, Mar 27, 2018 at 2:50 PM, Philip Zeyliger <[email protected]
> >
> >> > wrote:
> >> >
> >> > > Hi folks,
> >> > >
> >> > > I just sent off https://gerrit.cloudera.org/#/c/9743/ and
> >> > > https://issues.apache.org/jira/browse/IMPALA-4277 for GVD, which
> >> changes
> >> > > the default minicluster to be based on Hadoop 3.0, Hive 2.1, Sentry
> >> 2.0,
> >> > > and so on. This change *will not* be back-ported to 2.x.
> >> > >
> >> > > When you pull that change in, you'll need to re-build your
> minicluster
> >> > > with, e.g., ./buildall.sh -testdata -format -notests. This will pull
> >> in
> >> > the
> >> > > new dependencies, format your cluster, and load up all the data. As
> >> you
> >> > > know, it takes 1-2 hours.
> >> > >
> >> > > If you want to hold off, you can elso set export
> >> > > IMPALA_MINICLUSTER_PROFILE_OVERRIDE=2 in your environment.
> >> > >
> >> > > Note that this choice between versions happens at build time, and
> >> CMake
> >> > > depends on it. So, switching back and forth requires re-running
> CMake.
> >> > >
> >> > > Please let me know if you run into any trouble. This is a big enough
> >> that
> >> > > there may be some bumps on the road.
> >> > >
> >> > > -- Philip
> >> > >
> >> >
> >>
> >
>
