Looks like Ajantha already reverted it now in
https://github.com/apache/iceberg/pull/9815 so let's just keep it as is for
1.5.

As I listed in the PR just now, I think there are 3 options:
1. Salesforce can move it to a Salesforce GitHub domain and own it
2. my team can potentially move it to an Amazon-owned GitHub domain
(together with GlueCatalog) and collaborate there
3. we move it with other catalogs together to the new separated repo

For option 3, what is the latest plan? I remember we want to have more
devlist discussions from the last community sync, has anyone volunteered to
lead the discussion thread?

-Jack

On Tue, Feb 27, 2024 at 9:21 AM Ryan Blue <b...@tabular.io> wrote:

> I don't think we need to revert a deprecation. Deprecation gives people
> time to move off of something that won't be supported in the future and it
> doesn't make sense to me to delay letting people know that.
>
> On Mon, Feb 26, 2024 at 11:34 PM Ajantha Bhat <ajanthab...@gmail.com>
> wrote:
>
>> Looks like Salesforce is using the DynamoDB catalog in production.
>> https://github.com/apache/iceberg/pull/9783#issuecomment-1965781361
>>
>> They can provide more details.
>>
>> How about *reverting* the Deprecation for 1.5.0 release?
>> If finally concluded to be deprecated, can we deprecate it in 1.6.0?
>> I just don't want the upcoming RC4 to fail because of this and do RC5
>> just for it.
>>
>> - Ajantha
>>
>> On Fri, Feb 23, 2024 at 2:44 AM Drew <img...@gmail.com> wrote:
>>
>>> Hey everyone,
>>>
>>> Since it seems like we have met a consensus here, I can pick up the
>>> deprecation of DynamoDbCatalog. I submitted a PR that marks the catalog as
>>> deprecated and schedules it for complete removal in two releases starting
>>> with 1.6.0.
>>>
>>> Pr: https://github.com/apache/iceberg/pull/9783
>>>
>>> Thanks,
>>> Drew
>>>
>>> On Fri, Feb 16, 2024 at 5:24 PM Ajantha Bhat <ajanthab...@gmail.com>
>>> wrote:
>>>
>>>> +1 for deprecation and removal by 2.0 version.
>>>>
>>>> - Ajantha
>>>>
>>>> On Sat, Feb 17, 2024 at 4:23 AM Daniel Weeks <dwe...@apache.org> wrote:
>>>>
>>>>> +1 as well for deprecation
>>>>>
>>>>> On Fri, Feb 16, 2024 at 1:08 AM Jean-Baptiste Onofré <j...@nanthrax.net>
>>>>> wrote:
>>>>>
>>>>>> Perfect ! Thanks !
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On Thu, Feb 15, 2024 at 7:18 PM Jack Ye <yezhao...@gmail.com> wrote:
>>>>>> >
>>>>>> > Thanks for the feedback JB! Yes, I was originally intended to use
>>>>>> this thread to collect any concern of us flagging this catalog as
>>>>>> deprecated.
>>>>>> >
>>>>>> > If I don't receive any objection in the next 5 days, I will go
>>>>>> ahead to do that, and let the default 2 release full deprecation window
>>>>>> apply. And I will revive this thread again to double check when we plan 
>>>>>> to
>>>>>> remove it after 2 releases.
>>>>>> >
>>>>>> > Best,
>>>>>> > Jack Ye
>>>>>> >
>>>>>> > On Thu, Feb 15, 2024 at 2:33 AM Jean-Baptiste Onofré <
>>>>>> j...@nanthrax.net> wrote:
>>>>>> >>
>>>>>> >> Hi Jack,
>>>>>> >>
>>>>>> >> If we have a very low number of users and propose they move to
>>>>>> another
>>>>>> >> catalog, that makes sense to me.
>>>>>> >>
>>>>>> >> I think we can first flag DynamodbCatalog as deprecated (providing
>>>>>> a
>>>>>> >> message to the community and give time for users to move forward),
>>>>>> >> then we can plan a vote later to remove it.
>>>>>> >>
>>>>>> >> Regards
>>>>>> >> JB
>>>>>> >>
>>>>>> >> On Wed, Feb 14, 2024 at 7:11 PM Jack Ye <yezhao...@gmail.com>
>>>>>> wrote:
>>>>>> >> >
>>>>>> >> > Hi everyone,
>>>>>> >> >
>>>>>> >> > As discussed in community sync, I am raising a thread about
>>>>>> potentially deprecating DynamodbCatalog.
>>>>>> >> >
>>>>>> >> > I added it back in the day because of some customer
>>>>>> collaboration effort. Later another implementation was also added in 
>>>>>> pybut
>>>>>> at this point the specific customer has forked the implementation and is
>>>>>> maintaining their own catalog.
>>>>>> >> >
>>>>>> >> > Please comment if you have any production dependency or have any
>>>>>> concern about deprecating for this catalog, and we can discuss the path
>>>>>> forward.
>>>>>> >> >
>>>>>> >> > Best,
>>>>>> >> > Jack Ye
>>>>>>
>>>>>
>
> --
> Ryan Blue
> Tabular
>

Reply via email to