[ https://issues.apache.org/jira/browse/IMPALA-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Volker updated IMPALA-3643: -------------------------------- Fix Version/s: Not Applicable > AuthorizationTest.java fails on dev machine > ------------------------------------------- > > Key: IMPALA-3643 > URL: https://issues.apache.org/jira/browse/IMPALA-3643 > Project: IMPALA > Issue Type: Bug > Components: Frontend > Affects Versions: Impala 2.6.0 > Reporter: Lars Volker > Assignee: Lars Volker > Priority: Minor > Labels: flaky > Fix For: Not Applicable > > Attachments: com.cloudera.impala.analysis.AuthorizationTest.txt > > > [~dtsirogiannis] - I picked you as you look like the author of the relevant > parts of {AnalysisContext.java} and might have an idea what’s going on here; > feel free to find another person or assign back to me if you're swamped. > {{AuthorizationTest.java#TestSelect():498}} fails on my dev machine when > running this statement: > {noformat} > // Select from non-existent db. > AuthzError("select 1 from nodb.alltypes", > "User '%s' does not have privileges to execute 'SELECT' on: > nodb.alltypes"); > {noformat} > The error is the following: > {noformat} > User 'lv' does not have privileges to execute 'SELECT' on: default.nodb > expected: > User 'lv' does not have privileges to execute 'SELECT' on: nodb.alltypes > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at > com.cloudera.impala.analysis.AuthorizationTest.AuthzError(AuthorizationTest.java:2080) > at > com.cloudera.impala.analysis.AuthorizationTest.AuthzError(AuthorizationTest.java:2063) > at > com.cloudera.impala.analysis.AuthorizationTest.AuthzError(AuthorizationTest.java:2057) > at > com.cloudera.impala.analysis.AuthorizationTest.TestSelect(AuthorizationTest.java:498) > {noformat} > I tried to debug this and ended up in {{AnalysisContext.java:430}}. > {{tablePrivReqs}} contains two entries, {{default.nodb}} and > {{nodb.alltypes}}. The iteration starts with the former and thus the error is > raised with the wrong table name. > Do we expect both these entries in {{tablePrivReqs}}? If so, could this be > caused by my local JVM iterating elements of HashMaps in a different order? > My HEAD is at {{* 7167950 - Remove redundant test in > test_avro_schema_resolution.py (3 days ago) <Alex Behm>}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org