mskyrim opened a new pull request, #36562:
URL: https://github.com/apache/beam/pull/36562

   this fixes the issue raised here https://github.com/apache/beam/issues/35417 
   What happened?
   
   We are using an Apache Beam pipeline (v2.62.0) to ingest data read in 
Protobuf format, transform it into a Beam schema (dynamically), and then write 
it to an Iceberg table using IcebergIO.writeRows as the final step of the 
pipeline.
   We have noticed an issue when writing to Iceberg tables that are partitioned 
by the meta_processing_time field using the following specification:
   
(PartitionSpec.builderFor(contractIcebergSchema).month("meta_processing_time").build())
   Although the Parquet data files are correctly written under the expected 
monthly partition folders (e.g., path/2025-06/filename.parquet), when querying 
the table using Trino:
   select "$partition" , "$path",* from iceberg_table"
   
   The $partition metadata field incorrectly shows a value of "1970-07", while:
   
   the $path value is correctly referencing the meta_processing_time month 
(e.g., 'path/2025-06/filename.parquet')
   the actual meta_processing_time column in the data contains the correct 
timestamp value (e.g., '2025-06-24 11:06:06.187 +00:00')
   After running the following query in Trino:
   
   ALTER TABLE table_name EXECUTE optimize
   
   the $partition value is corrected and shows the expected value '2025-06'.
   We have upgraded to the latest Apache Beam version as well as the Iceberg 
core library, but the issue persists.
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable. This will automatically add a link to the 
pull request in the issue. If you would like the issue to automatically close 
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI or the [workflows 
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) 
to see a list of phrases to trigger workflows.
   


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