You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "alamb (via GitHub)" <gi...@apache.org> on 2024/11/07 22:56:22 UTC

[I] Proposal: Add `unsafe` option to disable UTF8 validation on parquet read [arrow-rs]

alamb opened a new issue, #6701:
URL: https://github.com/apache/arrow-rs/issues/6701

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   
   It is a pretty common usecase for systems (e.g. InfluxDB 3.0) to ingest data and write it as parquet files and then only ready parquet files that we wrote (and this are well formed) 
   
   Doing utf8 validation in the parquet reader take a significant amount of time for string data, likely leading to proposals to improve it like 
   - https://github.com/apache/arrow-rs/issues/6667
   
   However if the usecase is to speed up parquet data that is "trusted" maybe validating at all is unecessary.
   
   **Describe the solution you'd like**
   Add an `unsafe` parquet API to disable UTF8 validation during read for users
   
   **Describe alternatives you've considered**
   <!--
   A clear and concise description of any alternative solutions or features you've considered.
   -->
   
   **Additional context**
   <!--
   Add any other context or screenshots about the feature request here.
   -->
   


-- 
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: github-unsubscribe@arrow.apache.org.apache.org

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


Re: [I] Proposal: Add `unsafe` option to disable UTF8 validation on parquet read [arrow-rs]

Posted by "alamb (via GitHub)" <gi...@apache.org>.
alamb commented on issue #6701:
URL: https://github.com/apache/arrow-rs/issues/6701#issuecomment-2463389760

   We obviously wouldn't use this in DataFusion for clickbench (as it would basically be cheating) but we might very well do so internally in InfluxDB 3.0 or other places where re-validating the same UTF8 data we already wrote consumes CPU unecessarly


-- 
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: github-unsubscribe@arrow.apache.org

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