Re: Discussion about the location of language clients

I should have mentioned that Github does automatic redirection when you do a rename of a repository. But you're all right, the impact is possibly bigger than we can envision and it is probably not worth it. I took the liberty of creating iceberg-python a

Re: Discussion about the location of language clients

Thanks everyone for nice discussion. +1 for multi repo while keeping core spec and java implementation in apache/iceberg. Currently java is still most widely adopted and sophisticated implementation. We only need to help people to find other implementation by providing links in web page. From

Re: Discussion about the location of language clients

I wasn't at the discussion on Wednesday, but it sounds like there is support for moving to separate repos. Does anyone strongly object? I also agree with Steven on not renaming to iceberg-java. That's the repo where we keep the spec and Java is the reference implementation. Plus we don't want to b

Re: Discussion about the location of language clients

I am also on the side of separate repos for different languages. otherwise, the main repo can grow too big. iceberg.apache.org website can provide proper links to repos for different languages. I would be -1 on renaming apache/iceberg to apache/iceberg-java, as it can break external links to the m

Re: Discussion about the location of language clients

Hi everyone, Today I took a stab at the generation of wheels in Python (here's the PR if anyone is interested), and when testing this it would also kick off many unrelated CI jobs. This is just for two languages, and I'm not convinced that it will scal

Re: Discussion about the location of language clients

Hi all, first off, thanks Brian for starting the conversation and thanks Renjie for the write up. I'm also in the camp multi-repo because of the already mentioned benefits. One point I would like to add is that the potential drawback of having less visibility with multi-repos can be mitigate

Re: Discussion about the location of language clients

Renjie, you're amazing. I think you summarized this better than I could, so thank you for that. I'd like to pull in a user's feedback on Slack FWIW, I’m personally a fan of separate repos for the client libraries. > It keeps things more a bit more isolated (in a good way) and explorable > (rathe

Discussion about the location of language clients

Hi, all: In yesterday’s community sync we talked about the location of different language clients, and I think we all agree that there should be consistent behavior for these clients, but the decision has not been made yet. I want to continue the discussion here on the pros and cons of differen