kevinjqliu commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2755438192
@glesperance i just added #1856 please take a look
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
glesperance commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2755414983
@kevinjqliu whats the best palce to follow the roadmap now that we're
closing this?
--
This is an automated message from the Apache Git Service.
To respond to the message,
kevinjqliu commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2755018701
Closing this one. We've made a lot of progress since this issue was opened
last year.
See
* [0.7.0 release
notes](https://github.com/apache/iceberg-python/releases/tag
kevinjqliu closed issue #736: PyIceberg Near-Term Roadmap
URL: https://github.com/apache/iceberg-python/issues/736
--
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 unsubscrib
kevinjqliu commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2417742241
Thanks for the context @anoopj. @jaehyeon-kim looks like #651 is a feature
request. There's currently no committed date to implement it, I'll readjust the
roadmap to reflect
anoopj commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2417448465
@jaehyeon-kim That is correct. BigQuery Metastore is the replacement for
BigLake Metastore. I recommend adjusting the roadmap to skip BigLake metastore
and add support for BigQue
jaehyeon-kim commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2412464577
It look BigLake metastore is going to be replaced to BigQuery metastore. Is
the version 0.8.0 still relevant?
https://github.com/trinodb/trino/issues/20031#issuecomme
MehulBatra commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2143983698
> @Fokko can we add issues for creating tests and documentation for the new
features of 0.7.0 as good first issues?
@tusharchou: Whenever you create a new feature, you
tusharchou commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2133660186
@Fokko can we add issues for creating tests and documentation for the new
features of 0.7.0 as good first issues?
--
This is an automated message from the Apache Git Servic
Fokko commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2126667610
Sorry for the late reply, I was touching grass.
> @kevinjqliu @Fokko Where would something like the Iceberg Spark
create_changelog_view procedure fit in this roadmap? Is tha
tusharchou commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2125031765
@kevinjqliu @Fokko where would something like
https://github.com/apache/iceberg-python/issues/402 go?
--
This is an automated message from the Apache Git Service.
To respon
corleyma commented on issue #736:
URL: https://github.com/apache/iceberg-python/issues/736#issuecomment-2110652446
@kevinjqliu @Fokko Where would something like the Iceberg Spark
`create_changelog_view` procedure fit in this roadmap? Is that something that
might be tackled as part of the o
kevinjqliu opened a new issue, #736:
URL: https://github.com/apache/iceberg-python/issues/736
### Feature Request / Improvement
# PyIceberg 0.7.0
The main objective of 0.7.0 is to have partitioned writes (non-exhaustive
list :)
- [ ] Support partitioned appends:
https:/
13 matches
Mail list logo
