Hi Ori,
Iceberg doesn't impose a maximum number of partitions. We have a table with
1.2 million partitions that works quite well.
Iceberg stores a tuple of partition information with each file, to identify
the partition that file belongs to. This cost is constant so it doesn't
matter if you have
Thanks Jokob! I've reviewed the PR and will commit it and redeploy the site
once it's updated.
On Mon, Jan 6, 2020 at 11:47 AM Jakob Homan wrote:
> The website only lists the dev@, commits@ and private@ lists[1]. I've
> opened a PR[2] to add the issues@ list to make it more visible to new
> mem
The website only lists the dev@, commits@ and private@ lists[1]. I've
opened a PR[2] to add the issues@ list to make it more visible to new
members of the community.
-Jakob
[1] https://iceberg.incubator.apache.org/community/
[2] https://github.com/apache/incubator-iceberg/pull/724
On Mon, Jan 6,
Hi everyone,
Github updates are sent to iss...@iceberg.apache.org. Sorry for the
confusion. The background is that the notifications originally went to the
dev list, but the traffic was annoyingly high because it included not just
issue or PR creation, but also every individual comment. A few peop
I also think it’s a good idea to have an email thread dedicated to
reviews/issues.
- Anton
> On 6 Jan 2020, at 17:06, Wes McKinney wrote:
>
> I also joined the dev@ list to keep abreast of what's going on in
> Iceberg. If all of the development activity is happening on GitHub
> issues and pull
I also joined the dev@ list to keep abreast of what's going on in
Iceberg. If all of the development activity is happening on GitHub
issues and pull requests, then it seems like all of this activity
should be mirrored to _some_ mailing list, for example
github@iceberg.a.o. This creates a searchable
