pacman82 opened a new issue, #3362: URL: https://github.com/apache/arrow-rs/issues/3362
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> As the author of the upstream `odbc2parquet` I would like for `parquet` to support writing `Time` columns with `MicroSeconds` precision, so I can offer more precise types to my users. This is especially helpful if `odbc2parquet` is used as part of a data pipeline in which the next steps relies on legacy converted types, since these do not have pendant for `NanoSeconds` precision. Currently if I try to write a column of that type `parquet` emits a panic. ``` not implemented: Conversion for physical type INT64, converted type TIME_MICROS, value 334000000 ``` **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> If I am not mistaken the interface should just be analogous to writing Time columns with `NanoSeconds` precision. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> Lacking support in the parquet crate, I am unlikely to offer that improvement. **Additional context** <!-- Add any other context or screenshots about the feature request here. --> Here is the original issue that triggered support for Time in `odbc2parquet`: https://github.com/pacman82/odbc2parquet/issues/285 Sadly so far I can only offer it with Nanoseconds precision. -- 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-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
