{"push_id":1088129499,"size":1,"distinct_size":1,"ref":"refs/heads/add_impersonation_test","head":"36338d87824db727dbd57b5cd65cb3c1c29f3565","before":"93e16a887267e7d115bcc46d135905ef47b954db","commits":[{"sha":"36338d87824db727dbd57b5cd65cb3c1c29f3565","author":{"email":"3a78d7e80f916d2e7b5df3a43166c59218f27c4b@teradata.com","name":"Sanjay Sharma"},"message":"Add HDFS impersonation product tests\n\nAdd product tests that verify that HDFS impersonation is either enabled or\ndisabled.\n\nTo verify HDFS impersonation a table is created using the Hive connector.\nIf HDFS impersonation is enabled table data should belong to the Presto JDBC\nuser, otherwise it should belong to the Hadoop user defined\nin Presto configuration.\n\nThese tests are profile specific, and can't be run simultaneously on the\nproduct tests environment. In order to exclude such tests from a regular\ntest suite, that is being run on all the environments, the `profile_specific`\ntest group has been introduced. This group should be explicitly excluded\nfor the regular test runs, along with the `quarantine` and `big_query` groups.\nThen either the `hdfs_impersonation` or `hdfs_no_impersonation` group should\nbe included based on the environment configuration we are going to run\nproduct tests on.","distinct":true,"url":"https://api.github.com/repos/Teradata/presto/commits/36338d87824db727dbd57b5cd65cb3c1c29f3565"}]}