@cassandra.apache.org
Subject: Re: Role of Hadoop code in Cassandra 5.0
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
The actual removal in 6.0 means that this will not go away sooner than ... 2025
I'll get to it
tomorrow.
From: Jeremy Hanna
Sent: Thursday, March 16, 2023 22:27
To: dev@cassandra.apache.org
Subject: Re: Role of Hadoop code in Cassandra 5.0
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless you
>>>>>> I have couple more points ... I do not think that extracting it to a
>>>>>> separate repository is "win". That code is on Hadoop 1.0.3. We would be
>>>>>> spending a lot of work on extracting it just to extract 10 years old
>>>
: Re: Role of Hadoop code in Cassandra 5.0
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
Isn’t our deprecation rules that if we deprecate in 4.0.0 we can remove in 5.x,
but 4.x needs to
gt;> >>> > - - -- --- - -----
>>>>> >>> > Jacek Lewandowski
>>>>> >>> >
>>>>> >>> >
>>>>> >>> > czw., 9 mar 2023 o 18:07 Miklosovic, Stefan
>>>>&g
le more points ... I do not think that extracting it to
>> a separate repository is "win". That code is on Hadoop 1.0.3. We would be
>> spending a lot of work on extracting it just to extract 10 years old code
>> with occasional updates (in my humble opinion just to make it compilable
>> again if the code ar
gt; >>
>>> >> 1) leave it there so it will be like this is for next
years with questionable and diminishing usage
>>> >> 2) update it to Hadoop 3.3 (I wonder who is going to do that)
>>> >> 3) 2) and extract it to a separate reposit
t;> >> be spending a lot of work on extracting it just to extract 10 years
>> >>> >> old code with occasional updates (in my humble opinion just to make
>> >>> >> it compilable again if the code around changes). What good is in
>> >>> >&g
t? We would have one
> more place to take care of ... Now we at least have it all in one place.
> >>> >>
> >>> >> I believe we have four options:
> >>> >>
> >>> >> 1) leave it there so it will be like this is for next years
4) remove it
>
>
> From: Derek Chen-Becker
> Sent: Thursday, March 9, 2023 15:55
> To: dev@cassandra.apache.org
> Subject: Re: Role of Hadoop code in Cassandra 5.0
>
> NetApp Security WARNING: This is an external email. Do not click
Is there a ticket for that?
- - -- --- - -
Jacek Lewandowski
czw., 9 mar 2023 o 20:27 Mick Semb Wever napisał(a):
>
>
> On Thu, 9 Mar 2023 at 18:54, Brandon Williams wrote:
>
>> I think if we reach consensus here that decides it. I too vote to
>> deprecate in 4.1.x.
On Thu, 9 Mar 2023 at 18:54, Brandon Williams wrote:
> I think if we reach consensus here that decides it. I too vote to
> deprecate in 4.1.x. This means we would remove it in 5.0.
>
+1
t think that extracting it to a
> >>>>>>> separate repository is "win". That code is on Hadoop 1.0.3. We would
> >>>>>>> be spending a lot of work on extracting it just to extract 10 years
> >>>>>>> old code with occasional updates (in my humble opinion just t
p 1.0.3. We would be
>>>>>>> spending a lot of work on extracting it just to extract 10 years old
>>>>>>> code with occasional updates (in my humble opinion just to make it
>>>>>>> compilable again if the code around changes). What good i
e more place to take care of ... Now we at least have it
>>>>>> all in one place.
>>>>>>
>>>>>> I believe we have four options:
>>>>>>
>>>>>> 1) leave it there so it will be like this is for next years with
lace to take care of ... Now we at least have it
>>> >> all in one place.
>>> >>
>>> >> I believe we have four options:
>>> >>
>>> >> 1) leave it there so it will be like this is for next years with
>>> >> questionable and diminishing usage
>>> &
Deprecation would mean that the code has to be there whole 5.0 so we can remove
it for real in 6.0?
From: Ekaterina Dimitrova
Sent: Thursday, March 9, 2023 18:32
To: dev@cassandra.apache.org
Subject: Re: Role of Hadoop code in Cassandra 5.0
NetApp
>>
>> >> 1) leave it there so it will be like this is for next years with
>> questionable and diminishing usage
>> >> 2) update it to Hadoop 3.3 (I wonder who is going to do that)
>> >> 3) 2) and extract it to a separate repository but if we do 2) we can
>> just leave it there
&
inishing usage
> >> 2) update it to Hadoop 3.3 (I wonder who is going to do that)
> >> 3) 2) and extract it to a separate repository but if we do 2) we can
> just leave it there
> >> 4) remove it
> >>
> >>
> >> From: Derek Chen-Becker
&
_______________
>> From: Derek Chen-Becker
>> Sent: Thursday, March 9, 2023 15:55
>> To: dev@cassandra.apache.org
>> Subject: Re: Role of Hadoop code in Cassandra 5.0
>>
>> NetApp Security WARNING: This is an external email. Do not click links or
&g
3.3 (I wonder who is going to do that)
>> 3) 2) and extract it to a separate repository but if we do 2) we can just
>> leave it there
>> 4) remove it
>>
>> ____________
>> From: Derek Chen-Becker
>> Sent: Thursday, March 9
ract it to a separate repository but if we do 2) we can just
> leave it there
> 4) remove it
>
>
> From: Derek Chen-Becker
> Sent: Thursday, March 9, 2023 15:55
> To: dev@cassandra.apache.org
> Subject: Re: Role of Hadoop code in Cas
: Re: Role of Hadoop code in Cassandra 5.0
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
I think the question isn't "Who ... is still using that?" but more "are we
act
more years
again.
From: Derek Chen-Becker
Sent: Thursday, March 9, 2023 15:55
To: dev@cassandra.apache.org
Subject: Re: Role of Hadoop code in Cassandra 5.0
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless
I think the question isn't "Who ... is still using that?" but more "are we
actually going to support it?" If we're on a version that old it would
appear that we've basically abandoned it, although there do appear to have
been refactoring (for other things) commits in the last couple of years. I
wou
25 matches
Mail list logo
