zentol commented on code in PR #21221:
URL: https://github.com/apache/flink/pull/21221#discussion_r1045782253


##########
flink-architecture-tests/flink-architecture-tests-production/archunit-violations/b8900323-6aab-4e7e-9b17-f53b3c3dca46:
##########
@@ -17,11 +17,10 @@ Method 
<org.apache.flink.connector.hbase.sink.HBaseSinkFunction.prepareRuntimeCo
 Method 
<org.apache.flink.connector.hbase.sink.HBaseSinkFunction.prepareRuntimeConfiguration()>
 has return type <org.apache.hadoop.conf.Configuration> in 
(HBaseSinkFunction.java:0)
 Method 
<org.apache.flink.connector.hbase.source.HBaseRowDataLookupFunction.prepareRuntimeConfiguration()>
 calls method <org.apache.hadoop.conf.Configuration.get(java.lang.String)> in 
(HBaseRowDataLookupFunction.java:147)
 Method 
<org.apache.flink.connector.hbase.source.HBaseRowDataLookupFunction.prepareRuntimeConfiguration()>
 has return type <org.apache.hadoop.conf.Configuration> in 
(HBaseRowDataLookupFunction.java:0)
-Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.getHBaseConfiguration(org.apache.flink.configuration.ReadableConfig)>
 calls method <org.apache.hadoop.conf.Configuration.set(java.lang.String, 
java.lang.String)> in (HBaseConnectorOptionsUtil.java:113)
-Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.getHBaseConfiguration(org.apache.flink.configuration.ReadableConfig)>
 calls method <org.apache.hadoop.conf.Configuration.set(java.lang.String, 
java.lang.String)> in (HBaseConnectorOptionsUtil.java:114)
+Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.getHBaseConfiguration(org.apache.flink.configuration.ReadableConfig)>
 calls method <org.apache.hadoop.conf.Configuration.set(java.lang.String, 
java.lang.String)> in (HBaseConnectorOptionsUtil.java:101)
+Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.getHBaseConfiguration(org.apache.flink.configuration.ReadableConfig)>
 calls method <org.apache.hadoop.conf.Configuration.set(java.lang.String, 
java.lang.String)> in (HBaseConnectorOptionsUtil.java:102)
+Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.getHBaseConfiguration(org.apache.flink.configuration.ReadableConfig)>
 calls method <org.apache.hadoop.conf.Configuration.set(java.lang.String, 
java.lang.String)> in (HBaseConnectorOptionsUtil.java:108)
 Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.getHBaseConfiguration(org.apache.flink.configuration.ReadableConfig)>
 has return type <org.apache.hadoop.conf.Configuration> in 
(HBaseConnectorOptionsUtil.java:0)
-Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.lambda$getHBaseConfiguration$0(org.apache.hadoop.conf.Configuration,
 java.lang.Object, java.lang.Object)> calls method 
<org.apache.hadoop.conf.Configuration.set(java.lang.String, java.lang.String)> 
in (HBaseConnectorOptionsUtil.java:120)
-Method 
<org.apache.flink.connector.hbase.table.HBaseConnectorOptionsUtil.lambda$getHBaseConfiguration$0(org.apache.hadoop.conf.Configuration,
 java.lang.Object, java.lang.Object)> has parameter of type 
<org.apache.hadoop.conf.Configuration> in (HBaseConnectorOptionsUtil.java:0)

Review Comment:
   AFAICT this hasn't got anything to do with "merging" errors.
   
   The lambda issue was for having a Hadoop configuration _parameter_, a 
different error altogether, and that is now gone.
   
   I would assume that the parameter type check is just no longer applied to 
lambdas, presumably because when you define such a lambda you either
   a) access said type somewhere else (to pass as a parameter)
   b) pass the lambda as an argument, but then you get another violation anyway.
   
   (nevermind that this "architecture" test is pretty weird since it complains 
about _every single usage of external libraries_).



-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to