Re: [I] Pyarrow type error [iceberg-python]

2024-07-09 Thread via GitHub
HonahX closed issue #541: Pyarrow type error URL: https://github.com/apache/iceberg-python/issues/541 -- 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: is

Re: [I] Pyarrow type error [iceberg-python]

2024-04-08 Thread via GitHub
bigluck commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2042792612 @Fokko it sounds good to me! :) -- 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 t

Re: [I] Pyarrow type error [iceberg-python]

2024-04-08 Thread via GitHub
Fokko commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2042789157 Ciao @bigluck. Thanks for jumping in here. Until V3 is finalized, we can add a flag to cast a nanosecond to a microsecond precision. Would that work for you? -- This is an autom

Re: [I] Pyarrow type error [iceberg-python]

2024-04-08 Thread via GitHub
bigluck commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2042703204 So, `timestamp_ns` & `timestamptz_ns` has been added on the `v3` of the iceberg specs, pyiceberg right now supports `v1` &`v2`. In my case, the column has been generated b

Re: [I] Pyarrow type error [iceberg-python]

2024-04-08 Thread via GitHub
bigluck commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2042634726 I'm facing a similar issue in my code. Tested using main@7fcdb8d25dfa2498ba98a2b8e8d2b327d85fa7c9 (the commit after `Minor fixes, #523 followup (#563)` and `Cast data to I

Re: [I] Pyarrow type error [iceberg-python]

2024-03-24 Thread via GitHub
kevinjqliu commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2016890280 Hey @dev-goyal, do you mind posting a snippet of your example above? I think this is very similar to #520 In #520, the iceberg table is created with pyarrow schema. Int

Re: [I] Pyarrow type error [iceberg-python]

2024-03-23 Thread via GitHub
dev-goyal commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2016573605 Thanks @Fokko, makes sense! I was able to simply reduce precision on my end so it's not a big deal, but I figured it couldn't hurt to raise this. I wrote these data usin

Re: [I] Pyarrow type error [iceberg-python]

2024-03-23 Thread via GitHub
Fokko commented on issue #541: URL: https://github.com/apache/iceberg-python/issues/541#issuecomment-2016497750 @dev-goyal Thanks for raising this. It looks like that's a timestamp with nanosecond precision. Support for nanosecond timestamps is currently being added in the latest specificat

[I] Pyarrow type error [iceberg-python]

2024-03-22 Thread via GitHub
dev-goyal opened a new issue, #541: URL: https://github.com/apache/iceberg-python/issues/541 ### Apache Iceberg version 0.6.0 (latest release) ### Please describe the bug 🐞 Given a table like so: `In [36]: table Out[36]: matches( ... 14: player_last_