brkyvz opened a new pull request, #3608:
URL: https://github.com/apache/parquet-java/pull/3608

   <!--
   Thanks for opening a pull request!
   
   If you're new to Parquet-Java, information on how to contribute can be found 
here: https://parquet.apache.org/docs/contribution-guidelines/contributing
   
   Please open a GitHub issue for this pull request: 
https://github.com/apache/parquet-java/issues/new/choose
   and format pull request title as below:
   
       GH-${GITHUB_ISSUE_ID}: ${SUMMARY}
   
   or simply use the title below if it is a minor issue:
   
       MINOR: ${SUMMARY}
   
   -->
   
   ### Rationale for this change
   
   Introduces the reference implementation for the new LogicalTypeAnnotation 
File as discussed in this [design 
document](https://docs.google.com/document/d/1AiwrstqkwkBoOZqgOkm9JGwSMcNeHyLR7EEj1CVqpZQ/edit?tab=t.0#heading=h.k8qyue4jj4rn)
   
   
   ### What changes are included in this PR?
   
   Introduces a new LogicalTypeAnnotation called FILE. It enforces that a group 
with this type annotation have the following fields by name:
   ```
   path                                 STRING  NOT NULL
   size                         INT64                   
   offset                               INT64           
   etag                         STRING
   ```
   
   
   ### Are these changes tested?
   
   Yes, unit tested
   
   ### Are there any user-facing changes?
   
   Introduces a new LogicalTypeAnnotation called FILE
   
   <!-- Please uncomment the line below and replace ${GITHUB_ISSUE_ID} with the 
actual Github issue id. -->
   <!-- Closes #${GITHUB_ISSUE_ID} -->
   


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