You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iceberg.apache.org by "Driesprong, Fokko" <fo...@apache.org> on 2023/02/17 09:37:04 UTC
[DISCUSS] Removing python_legacy from the repo
Hi all,
I'd want to discuss removing the python_legacy codebase from the
repository. I think we've reached the point where the new library has
feature parity with the legacy one, so I think that this would be a good
time to remove the legacy one. The main reason for me is to avoid confusion
for newcomers to the project. Let me know what you think, and if you have
any questions or concerns.
Kind regards,
Fokko Driesprong
Re: [DISCUSS] Removing python_legacy from the repo
Posted by "Driesprong, Fokko" <fo...@apache.org>.
Hi everyone,
As discussed today at the Iceberg Python sync, I've created a PR for
removing python_legacy from the repo:
https://github.com/apache/iceberg/pull/6960
Again, I would like to thank all the authors working on this! It was a
great inspiration for PyIceberg.
Kind regards,
Fokko Driesprong
Op wo 22 feb 2023 om 04:36 schreef Jun H. <ju...@gmail.com>:
> +1 for removing it. Thanks Fokko.
>
> Jun
>
> On Feb 21, 2023, at 7:47 AM, Daniel Weeks <dw...@apache.org> wrote:
>
>
> +1 for removal
>
> On Tue, Feb 21, 2023, 7:38 AM Jack Ye <ye...@gmail.com> wrote:
>
>> +1 for removing it!
>>
>> Thanks,
>> Jack Ye
>>
>> On Fri, Feb 17, 2023 at 4:18 PM Steve Zhang
>> <ho...@apple.com.invalid> wrote:
>>
>>> Thank you Fokko and Ryan for your great work to reach feature parity.
>>> pyiceberg is the way to go!
>>>
>>> Thanks,
>>> Steve Zhang
>>>
>>>
>>>
>>> On Feb 17, 2023, at 8:29 AM, Ryan Blue <bl...@tabular.io> wrote:
>>>
>>> +1 for removing it. And it's great to see the new one reaching feature
>>> parity!
>>>
>>> On Fri, Feb 17, 2023 at 1:37 AM Driesprong, Fokko <fo...@apache.org>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'd want to discuss removing the python_legacy codebase from the
>>>> repository. I think we've reached the point where the new library has
>>>> feature parity with the legacy one, so I think that this would be a good
>>>> time to remove the legacy one. The main reason for me is to avoid confusion
>>>> for newcomers to the project. Let me know what you think, and if you have
>>>> any questions or concerns.
>>>>
>>>> Kind regards,
>>>> Fokko Driesprong
>>>>
>>>
>>>
>>> --
>>> Ryan Blue
>>> Tabular
>>>
>>>
>>>
Re: [DISCUSS] Removing python_legacy from the repo
Posted by "Jun H." <ju...@gmail.com>.
+1 for removing it. Thanks Fokko.
Jun
> On Feb 21, 2023, at 7:47 AM, Daniel Weeks <dw...@apache.org> wrote:
>
>
> +1 for removal
>
>> On Tue, Feb 21, 2023, 7:38 AM Jack Ye <ye...@gmail.com> wrote:
>> +1 for removing it!
>>
>> Thanks,
>> Jack Ye
>>
>>> On Fri, Feb 17, 2023 at 4:18 PM Steve Zhang <ho...@apple.com.invalid> wrote:
>>> Thank you Fokko and Ryan for your great work to reach feature parity.
>>> pyiceberg is the way to go!
>>>
>>> Thanks,
>>> Steve Zhang
>>>
>>>
>>>
>>>> On Feb 17, 2023, at 8:29 AM, Ryan Blue <bl...@tabular.io> wrote:
>>>>
>>>> +1 for removing it. And it's great to see the new one reaching feature parity!
>>>>
>>>>> On Fri, Feb 17, 2023 at 1:37 AM Driesprong, Fokko <fo...@apache.org> wrote:
>>>>> Hi all,
>>>>>
>>>>> I'd want to discuss removing the python_legacy codebase from the repository. I think we've reached the point where the new library has feature parity with the legacy one, so I think that this would be a good time to remove the legacy one. The main reason for me is to avoid confusion for newcomers to the project. Let me know what you think, and if you have any questions or concerns.
>>>>>
>>>>> Kind regards,
>>>>> Fokko Driesprong
>>>>
>>>>
>>>> --
>>>> Ryan Blue
>>>> Tabular
>>>
Re: [DISCUSS] Removing python_legacy from the repo
Posted by Daniel Weeks <dw...@apache.org>.
+1 for removal
On Tue, Feb 21, 2023, 7:38 AM Jack Ye <ye...@gmail.com> wrote:
> +1 for removing it!
>
> Thanks,
> Jack Ye
>
> On Fri, Feb 17, 2023 at 4:18 PM Steve Zhang
> <ho...@apple.com.invalid> wrote:
>
>> Thank you Fokko and Ryan for your great work to reach feature parity.
>> pyiceberg is the way to go!
>>
>> Thanks,
>> Steve Zhang
>>
>>
>>
>> On Feb 17, 2023, at 8:29 AM, Ryan Blue <bl...@tabular.io> wrote:
>>
>> +1 for removing it. And it's great to see the new one reaching feature
>> parity!
>>
>> On Fri, Feb 17, 2023 at 1:37 AM Driesprong, Fokko <fo...@apache.org>
>> wrote:
>>
>>> Hi all,
>>>
>>> I'd want to discuss removing the python_legacy codebase from the
>>> repository. I think we've reached the point where the new library has
>>> feature parity with the legacy one, so I think that this would be a good
>>> time to remove the legacy one. The main reason for me is to avoid confusion
>>> for newcomers to the project. Let me know what you think, and if you have
>>> any questions or concerns.
>>>
>>> Kind regards,
>>> Fokko Driesprong
>>>
>>
>>
>> --
>> Ryan Blue
>> Tabular
>>
>>
>>
Re: [DISCUSS] Removing python_legacy from the repo
Posted by Jack Ye <ye...@gmail.com>.
+1 for removing it!
Thanks,
Jack Ye
On Fri, Feb 17, 2023 at 4:18 PM Steve Zhang <ho...@apple.com.invalid>
wrote:
> Thank you Fokko and Ryan for your great work to reach feature parity.
> pyiceberg is the way to go!
>
> Thanks,
> Steve Zhang
>
>
>
> On Feb 17, 2023, at 8:29 AM, Ryan Blue <bl...@tabular.io> wrote:
>
> +1 for removing it. And it's great to see the new one reaching feature
> parity!
>
> On Fri, Feb 17, 2023 at 1:37 AM Driesprong, Fokko <fo...@apache.org>
> wrote:
>
>> Hi all,
>>
>> I'd want to discuss removing the python_legacy codebase from the
>> repository. I think we've reached the point where the new library has
>> feature parity with the legacy one, so I think that this would be a good
>> time to remove the legacy one. The main reason for me is to avoid confusion
>> for newcomers to the project. Let me know what you think, and if you have
>> any questions or concerns.
>>
>> Kind regards,
>> Fokko Driesprong
>>
>
>
> --
> Ryan Blue
> Tabular
>
>
>
Re: [DISCUSS] Removing python_legacy from the repo
Posted by Steve Zhang <ho...@apple.com.INVALID>.
Thank you Fokko and Ryan for your great work to reach feature parity.
pyiceberg is the way to go!
Thanks,
Steve Zhang
> On Feb 17, 2023, at 8:29 AM, Ryan Blue <bl...@tabular.io> wrote:
>
> +1 for removing it. And it's great to see the new one reaching feature parity!
>
> On Fri, Feb 17, 2023 at 1:37 AM Driesprong, Fokko <fokko@apache.org <ma...@apache.org>> wrote:
> Hi all,
>
> I'd want to discuss removing the python_legacy codebase from the repository. I think we've reached the point where the new library has feature parity with the legacy one, so I think that this would be a good time to remove the legacy one. The main reason for me is to avoid confusion for newcomers to the project. Let me know what you think, and if you have any questions or concerns.
>
> Kind regards,
> Fokko Driesprong
>
>
> --
> Ryan Blue
> Tabular
Re: [DISCUSS] Removing python_legacy from the repo
Posted by Ryan Blue <bl...@tabular.io>.
+1 for removing it. And it's great to see the new one reaching feature
parity!
On Fri, Feb 17, 2023 at 1:37 AM Driesprong, Fokko <fo...@apache.org> wrote:
> Hi all,
>
> I'd want to discuss removing the python_legacy codebase from the
> repository. I think we've reached the point where the new library has
> feature parity with the legacy one, so I think that this would be a good
> time to remove the legacy one. The main reason for me is to avoid confusion
> for newcomers to the project. Let me know what you think, and if you have
> any questions or concerns.
>
> Kind regards,
> Fokko Driesprong
>
--
Ryan Blue
Tabular