rdblue commented on code in PR #3709:
URL: https://github.com/apache/parquet-java/pull/3709#discussion_r3884264584


##########
dev/check-parquet-thrift-release.sh:
##########
@@ -0,0 +1,82 @@
+#!/usr/bin/env bash
+#
+# 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.
+
+# Verifies that the parquet-format.version sidecar file is tracking a released 
parquet-format
+# version and that the inlined parquet.thrift byte-matches the upstream file 
at that version.

Review Comment:
   I think that this should be removed, or at least changed to check against 
the `parquet-format.version` file and nothing else. We do need to be able to 
check the state of the thrift file, but that has little to do with releases. 
Plus, the file is version controlled, so we should be able to easily tell when 
it was modified and where the content came from by looking at 
parquet-format.version.



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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to