;
> >>> On the client-side, libraries themselves should be avoiding making
> >>> Cassandra version checks when detecting capabilities. There are a
> >> few
> >>> exceptions, such as system table parsing for schema & peers,
&g
client-side, libraries themselves should be avoiding making
>>> Cassandra version checks when detecting capabilities. There are a
>> few
>>> exceptions, such as system table parsing for schema & peers,
>>> but those aren't related to the protocol.
>>
>
> > Thanks,
> > Andy
> >
> >
> >
> >
> >
> > On Tue, Feb 18, 2020 at 1:22 PM Nate McCall
> wrote:
> > >
> > > [Moving to new message thread]
> > >
> > > Than
> >
> > Thanks for bringing this up, Jordan.
> >
> > IIRC, this was more a convention than a technical reason. Though I could
> be
> > completely misremembering this.
> >
> > -- Forwarded message -
> &g
protocol.
> > >
> > > Thanks,
> > > Andy
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Feb 18, 2020 at 1:22 PM Nate McCall
> wrote:
> > > >
> > > > [Moving to new message thread]
> > > >
> > > Thanks for bringing this up, Jordan.
> > >
> > > IIRC, this was more a convention than a technical reason. Though I
> could
> > be
> > > completely misremembering this.
> > >
> > > -- Forwarded message -
>
> > completely misremembering this.
> >
> > -- Forwarded message -
> > From: Jordan West
> > Date: Wed, Feb 19, 2020 at 10:13 AM
> > Subject: Re: 20200217 4.0 Status Update
> > To:
> >
> >
> > On Mon, Feb 17, 2020 at 12:52
could be
> completely misremembering this.
>
> -- Forwarded message -
> From: Jordan West
> Date: Wed, Feb 19, 2020 at 10:13 AM
> Subject: Re: 20200217 4.0 Status Update
> To:
>
>
> On Mon, Feb 17, 2020 at 12:52 PM Jeff Jirsa wrote:
>
> >
> >
[Moving to new message thread]
Thanks for bringing this up, Jordan.
IIRC, this was more a convention than a technical reason. Though I could be
completely misremembering this.
-- Forwarded message -
From: Jordan West
Date: Wed, Feb 19, 2020 at 10:13 AM
Subject: Re: 20200217 4.0
Moving to a new thread.
On Wed, Feb 19, 2020 at 10:13 AM Jordan West wrote:
> On Mon, Feb 17, 2020 at 12:52 PM Jeff Jirsa wrote:
>
> >
> > beyond the client proto change being painful for anything other than
> major
> > releases
> >
> >
> This came up during the community meeting today and I wa
On Mon, Feb 17, 2020 at 12:52 PM Jeff Jirsa wrote:
>
> beyond the client proto change being painful for anything other than major
> releases
>
>
This came up during the community meeting today and I wanted to bring a
question about it to the list: could someone who is *very* familiar with
the cli
> On Feb 17, 2020, at 12:52 PM, Jeff Jirsa wrote:
>
> Hard to see an argument for CASSANDRA-2848 being in scope for 4.0 (beyond the
> client proto change being painful for anything other than major releases).
>
Even if it doesn't affect v4 protocol?
Dinesh
--
Hard to see an argument for CASSANDRA-2848 being in scope for 4.0 (beyond the
client proto change being painful for anything other than major releases).
> On Feb 17, 2020, at 12:43 PM, Jon Meredith wrote:
>
> My turn to give an update on 4.0 status. The 4.0 board created by Josh can
> be
My turn to give an update on 4.0 status. The 4.0 board created by Josh can
be found at
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355.
We have 94 unresolved tickets marked against the 4.0 release. [1]
Things seem to have settled into a phase of working to resolve issues,
14 matches
Mail list logo
