kgyrtkirk commented on a change in pull request #794: HIVE-21884
URL: https://github.com/apache/hive/pull/794#discussion_r335326803
##########
File path: metastore/scripts/upgrade/hive/hive-schema-4.0.0.hive.sql
##########
@@ -1552,3 +1611,41 @@ WHERE
AND (P.`PRINCIPAL_NAME`=current_user() AND P.`PRINCIPAL_TYPE`='USER'
OR ((array_contains(current_groups(), P.`PRINCIPAL_NAME`) OR
P.`PRINCIPAL_NAME` = 'public') AND P.`PRINCIPAL_TYPE`='GROUP'))
AND P.`TBL_PRIV`='SELECT' AND P.`AUTHORIZER`=current_authorizer());
+
+
+drop view SCHEDULED_QUERIES ;
+create or replace view SCHEDULED_QUERIES as
Review comment:
I did this for 2 reasons: 1 was the timestamp you mentioned; the other thing
is to be able to join multiple tables.
I'm not sure how close are we to the standard...but there is also a
"COMPACTIONS" I haven't checked but that doesn't seem to be standard to me...
I think about `information_schema` as a might be usefull schema for db
administrators... if we want to limit the information_schema to standard stuff;
that might make sense...but I see value creating views like this - which might
help people (and me) get around...we may put the nonstandard stuff into some
different database - but I think as long as the name of the view doesn't
interfere with a standard one it might be okayish here as well...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
