Hello everyone, recently on Ranger, we noticed that when enabling users in a security zone, they are unable to see tables in a database through Impala. When connecting via JDBC through the command line or directly from HUE, they can view the tables and their respective data, but if all of this is done through Impala, they have no visibility at all. We have 4 clusters, and all of them have the same type of configuration and permissions, but we encounter the issue in 3 of these clusters. All configurations in Ranger have been checked and appear to be correct in all environments. At this point, I have no idea where to begin the analysis of the problem. Also, there are no access issues reported from Ranger to tables in the security zone, and there are no error logs or access denied logs. I realize that without providing an error log, it's difficult to conduct an analysis, but perhaps some of you have suggestions on where to start investigating the problem. Have any of you ever encountered a similar case? Thanks!!! ... View more

Hello everyone, my team using TEZ, in particular Hive, has noticed that during an insert with a very simple select a single parquet file of 1.5 gb per partition is generated in the output table. To try to remedy the problem, a number of settings were used at the session level but had no effect. Below are the sets used at the session level: SET hive.execution.engine=tez; SET hive.exec.dynamic.partition=true; SET hive.exec.dynamic.partition.mode=nonstrict; SET hive.optimise.sort.dynamic.partition.threshold=0; --SET tez.grouping.max-size=268435456; --SET hive.exec.reducers.bytes.per.reducer=536870912; --SET tez.grouping.split-count=18; SET hive.vectorized.execution.reduce.enabled = true; SET hive.vectorized.execution.reduce.groupby.enabled = true; --SET hive.tez.auto.reducer.parallelism=false; --SET mapred.reduce.tasks=12; --SET hive.tez.partition.size=104857600; --SET hive.tez.partition.num=10; SET hive.parquet.output.block.size=104857600; I would like to ask if there is a way to always have parquet type files but broken up into smaller files as shown in the image below We cannot understand what the cause might be. Files structured in this way do not guarantee sufficient parallelism for other jobs present (such as sqoop) ... View more