[jira] [Updated] (ARROW-2555) [Python] Provide an option to convert on coerce_timestamps instead of error
[
https://issues.apache.org/jira/browse/ARROW-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney updated ARROW-2555:
Fix Version/s: (was: 0.13.0)
0.11.0
> [Python] Provide an option to convert on coerce_timestamps instead of error
> ---
>
> Key: ARROW-2555
> URL: https://issues.apache.org/jira/browse/ARROW-2555
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
>Reporter: Uwe L. Korn
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.11.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> At the moment, we error out on {{coerce_timestamps='ms'}} on
> {{pyarrow.parquet.write_table}} if the data contains a timestamp that would
> loose information when converted to milliseconds. In a lot of cases the user
> does not care about this granularity and rather wants the comfort
> functionality that the timestamp are stored regardlessly in Parquet. Thus we
> should provide an option to ignore the error and do the lossy conversion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-2555) [Python] Provide an option to convert on coerce_timestamps instead of error
[
https://issues.apache.org/jira/browse/ARROW-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ARROW-2555:
--
Labels: pull-request-available (was: )
> [Python] Provide an option to convert on coerce_timestamps instead of error
> ---
>
> Key: ARROW-2555
> URL: https://issues.apache.org/jira/browse/ARROW-2555
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
>Reporter: Uwe L. Korn
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.13.0
>
>
> At the moment, we error out on {{coerce_timestamps='ms'}} on
> {{pyarrow.parquet.write_table}} if the data contains a timestamp that would
> loose information when converted to milliseconds. In a lot of cases the user
> does not care about this granularity and rather wants the comfort
> functionality that the timestamp are stored regardlessly in Parquet. Thus we
> should provide an option to ignore the error and do the lossy conversion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-2555) [Python] Provide an option to convert on coerce_timestamps instead of error
[
https://issues.apache.org/jira/browse/ARROW-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe L. Korn updated ARROW-2555:
---
Fix Version/s: (was: 0.11.0)
0.13.0
> [Python] Provide an option to convert on coerce_timestamps instead of error
> ---
>
> Key: ARROW-2555
> URL: https://issues.apache.org/jira/browse/ARROW-2555
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
>Reporter: Uwe L. Korn
>Priority: Major
> Fix For: 0.13.0
>
>
> At the moment, we error out on {{coerce_timestamps='ms'}} on
> {{pyarrow.parquet.write_table}} if the data contains a timestamp that would
> loose information when converted to milliseconds. In a lot of cases the user
> does not care about this granularity and rather wants the comfort
> functionality that the timestamp are stored regardlessly in Parquet. Thus we
> should provide an option to ignore the error and do the lossy conversion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ARROW-2555) [Python] Provide an option to convert on coerce_timestamps instead of error
[
https://issues.apache.org/jira/browse/ARROW-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Pitrou updated ARROW-2555:
--
Fix Version/s: (was: 0.10.0)
0.11.0
> [Python] Provide an option to convert on coerce_timestamps instead of error
> ---
>
> Key: ARROW-2555
> URL: https://issues.apache.org/jira/browse/ARROW-2555
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
>Reporter: Uwe L. Korn
>Priority: Major
> Fix For: 0.11.0
>
>
> At the moment, we error out on {{coerce_timestamps='ms'}} on
> {{pyarrow.parquet.write_table}} if the data contains a timestamp that would
> loose information when converted to milliseconds. In a lot of cases the user
> does not care about this granularity and rather wants the comfort
> functionality that the timestamp are stored regardlessly in Parquet. Thus we
> should provide an option to ignore the error and do the lossy conversion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
