[
https://issues.apache.org/jira/browse/ARROW-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487205#comment-17487205
]
Joris Van den Bossche edited comment on ARROW-15496 at 2/4/22, 5:57 PM:
------------------------------------------------------------------------
Short term it will probably be more useful to actually switch the default to a
more recent version that can handle those types (but I think we are planning to
do that in the next release? -> ARROW-12203). But yes, aside from that I agree
that a warning might be useful.
was (Author: jorisvandenbossche):
Short term it will probably be more useful to actually switch the default to a
more recent version that can handle those types (but I think we are planning to
do that in the next release?). But yes, aside from that I agree that a warning
might be useful.
> [C++][Python] Log warning when user tries to write parquet table with
> incompatible type
> ---------------------------------------------------------------------------------------
>
> Key: ARROW-15496
> URL: https://issues.apache.org/jira/browse/ARROW-15496
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++, Parquet, Python
> Reporter: Grant Williams
> Priority: Minor
> Labels: typeinfo, warnings
> Fix For: 8.0.0
>
>
> Could we get a logged warning when a user tries to
> `pyarrow.parquet.write_table()` with `version=1.0` and a schema that contains
> an incompatible `uint32()` type? I don't think the behavior to upcast to an
> `int64()` is immediately obvious (although the docs are clear on it) and I
> think it would help prevent some confusion for other users.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
