singhpk234 commented on code in PR #1402:
URL: https://github.com/apache/polaris/pull/1402#discussion_r2056728602


##########
plugins/spark/v3.5/regtests/Dockerfile:
##########
@@ -0,0 +1,48 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+FROM docker.io/apache/spark:3.5.5-java17

Review Comment:
   Generally the jvm in CI are marked as stamp of approval that this works for 
this jvm version both runtime and compile wise, building these in JVM requires 
special flags as per JVM version. 
   Saying this from my past experience of upgrading Iceberg with JDK 17 : 
https://github.com/apache/iceberg/pull/7391
   
   if we can only assert polaris spark client with JDK 17, then we should have 
only JDK 17
   
   If we are saying polaris-spark client will work on java 21 (both build and 
runtime) then i think this is fine to have JDK 21, (though i would like to 
understand more on how this is guaranteed, when spark doesn't do that ?)
   
   prev tests were not building spark client of their own, they were using it, 
just asserting the Polaris is ok to work with 21 so 21 in CI made sense.
   
   Atleast thats my read from it.



-- 
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: issues-unsubscr...@polaris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to