Fix misuse of HashSet::new

Fix a case where the column index was misused as a HashSet capacity parameter.
trinodb · Sep 16, 2020 · d8cbadf · d8cbadf
1 parent ebee077
commit d8cbadf
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/presto-hive/src/main/java/io/prestosql/plugin/hive/HivePageSourceProvider.java b/presto-hive/src/main/java/io/prestosql/plugin/hive/HivePageSourceProvider.java
@@ -362,7 +362,7 @@ public static List<ColumnMapping> buildColumnMappings(
                     }
 
                     checkArgument(
-                            projectionsForColumn.computeIfAbsent(column.getBaseHiveColumnIndex(), HashSet::new).add(column.getHiveColumnProjectionInfo()),
+                            projectionsForColumn.computeIfAbsent(column.getBaseHiveColumnIndex(), columnIndex -> new HashSet<>()).add(column.getHiveColumnProjectionInfo()),
                             "duplicate column in columns list");
 
                     // Add regular mapping if projection is valid for partition schema, otherwise add an empty mapping