CQL Tuples & CQL Grammar

[Claude Warren]

I have been looking at  CqlParser.g4 file for cql3  and have a question
about assignment tuples.  The assignment tuple is defined as :

assignmentTuple
   : syntaxBracketLr (
 constant ((syntaxComma constant)* | (syntaxComma assignmentTuple)*) |
 assignmentTuple (syntaxComma assignmentTuple)*
 ) syntaxBracketRr
   ;

which I read to be ( constant [, constant | tuple ... ]) or ( tuple [,
tuple...]) .  So the construct ((4 ,5 ), 6, (7, 8)) is not a legal tuple.2
questions:

   1.  Is my interpretation of the grammar correct?
   2. Is my example tuple supposed to be allowed?


Claude

-- 

[image: Instaclustr logo]


*Claude Warren*

Principal Software Engineer

Instaclustr

Re: New Apache Cassandra Group on LinkedIn

[Erick Ramirez]

I really like Melissa's idea of having a company instead for higher
visibility and members not having to join a group to see the activity. It
also makes it easy to tag the company in posts and get more engagement that
way. Cheers!

Re: New Apache Cassandra Group on LinkedIn

[Melissa Logan]

I agree there should be an official LinkedIn page for the project hosted by
the community. It's an easy way for people to stay current.

If the goal of the new LinkedIn page is to publicly and broadly share what
the Cassandra community is doing, one solution would be to change the new
Cassandra page from a "group" page to a "company" page.

Company pages show all posts publicly by default, and admins don't have to
manage requests to join. Anyone can "follow" the page and see/share the
posts -- while only allowing community admins to publish. This would also
require less care and feeding from community admins. (What I don't know if
it's easy to "convert" a group page to company or if it requires starting
from scratch.)

Then, admins of the existing "group" page could repost any/all items from
the community page to keep people informed.

This solution could help both pages achieve their goals of spreading the
word about Cassandra.


On Wed, Mar 9, 2022 at 10:39 AM Patrick McFadin  wrote:

> I'm not sure if they can merge groups but from what I'm reading that
> wouldn't work either. What I'm seeing is a desire to not "promote vendors"
> which I believe is working against the project's self-interest. LinkedIn is
> the perfect place to do it. The allergic reaction the project has taken for
> vendors has made our ecosystem look weak when that's not really the case.
> Temporal, Prometheus, Feast, Orkes (to just name a few) all have Cassandra
> integrations but you would never know that by looking at any official
> Cassandra communication because ecosystem == vendor == bad. The result is
> that Cassandra looks like an island that will never help this project grow.
>
> On Wed, Mar 9, 2022 at 9:20 AM Jeremy Hanna 
> wrote:
>
>> Is it possible to ask someone at linkedin to merge the groups together so
>> that it's managed by the PMC but with the explicit permission of the people
>> running the other group?  In the past, I know that Twitter does things like
>> that in terms of handles and followers.  Is that a desirable outcome?
>>
>> On Mar 9, 2022, at 11:00 AM, Benjamin Lerer  wrote:
>>
>> Hi Patrick,
>> Thanks for reaching out. Effectively the discussion has happened between
>> the PMC members.
>> To explain the context, we wanted to have an official group on Linkedin
>> to publish news about the project as we do through the @cassandra handler
>> on Twitter. We wanted a group that was vendor independent and focused on
>> Apache Cassandra and its ecosystem.
>> To be fully transparent, we had no idea that you were in charge of the
>> Apache Cassandra Users group as it appears managed by Lynn Bender and
>> Joanna Kapel. The group also appears to promote different vendors which is
>> something that we wanted to avoid.
>> Having to post things under Lynn's name was also an issue for us as we
>> wished the merits to go to the right persons.
>>
>> Now, I am sure that we can work out some solution that will benefit the
>> community. :-)
>>
>> Le mer. 9 mars 2022 à 15:56, Patrick McFadin  a
>> écrit :
>>
>>> I feel like this needs to be a discussion held on the public mailing
>>> list. I have been running the Apache Cassandra Users group on LinkedIn for
>>> years after taking it over from Lynn Bender.
>>> https://www.linkedin.com/groups/3803052/
>>>
>>> We have over 7500 members and had its ups and downs but it's been pretty
>>> consistent as a professional resource on LinkedIn. I'm not sure what there
>>> is to gain by creating competing groups. If we need more managers in the
>>> group that's fine but somebody just needed to ask. It's clear that this
>>> discussion happened somewhere else and this was just an announcement.
>>>
>>> Patrick
>>>
>>> On Thu, Mar 3, 2022 at 3:41 AM Benjamin Lerer  wrote:
>>>
 Hi everybody,

 We just created a new Apache Cassandra group on LinkedIn (
 https://www.linkedin.com/groups/9159443/).

 This group will be managed by our community and will respect vendor
 neutrality.
 Do not hesitate to join and share your experiences or blog posts with
 us :-)

>>>
>>

-- 
Melissa Logan (she/her)
Principal, Constantia.io
LinkedIn  | Twitter

Re: GSOD 2022

[Lorina Poland]

Yes, in that case, it sounds like much more than I can support as well.
Perhaps next year we'll be in a position to participate.

Lorina

On Wed, Mar 9, 2022 at 8:57 AM Dinesh Joshi  wrote:

> I looked into the GSoD rules for this year and they have changed
> significantly. Critically, the process requires organizations to collect a
> list of projects and apply to Google for a grant. This includes project
> ideas, budget and metrics for success. If the proposal is accepted Google
> will issue a grant and expect the organizations to select and pay the
> technical writers. This is a significant change from prior years and I
> don't think, we (Cassandra community), are setup for this. We need the ASF
> to apply as an organization as it requires a legal entity to sponsor the
> whole process including payments. This has come up in a separate discussion
> on comdev so we'll see how it goes. As GSoD deadline is March 25, I am not
> sure if we can participate.
>
> > On Mar 8, 2022, at 5:13 PM, Dinesh Joshi  wrote:
> >
> > I haven't looked into GSoD this year. However, the scope of a GSoD
> project has to be sufficient for the amount of time that is allocated by
> GSoD. They had 2 project lengths when we last participated - short & long.
> Projects need to be defined accordingly. It is a lot of work and I
> personally don't have time to select and mentor the technical writers. I
> can definitely help guide the application process as I think we also
> require someone from the PMC to actually submit the application. Nate
> helped me out when we last participated in GSoD so I'll be happy to help
> out on that front.
> >
> > Here's the page we created for tracking the GSoD Participation and
> project ideas:
> https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+GSoD+2019+application
> >
> > It would be a good idea to do something similar and get a sense of where
> our documentation is lacking and then proceed from there.
> >
> >> On Mar 8, 2022, at 1:56 PM, Lorina Poland  wrote:
> >>
> >> I'm willing to take the lead on GSoD. Let me think about what projects
> I think would benefit the docs.
> >>
> >> Lorina
> >>
> >> On 2022/03/08 16:03:48 Paulo Motta wrote:
> >>> Any of the docs contributors interested in taking the lead on this?
> Perhaps
> >>> Dinesh could share some tips on how to create the GSoD application.
> >>>
> >>> I think there is a lot of documentation that needs to be
> created/migrated,
> >>> would be nice to have some external help on this.
> >>>
> >>> For instance, some virtual tables were added but we have no
> documentation
> >>> on them. Perhaps we could have a GSoD project to better document
> Virtual
> >>> Tables?
> >>>
> >>> Em seg., 7 de mar. de 2022 às 17:54, Deepak Vohra 
> >>> escreveu:
> >>>
>  Has anyone applied for GSOD this year?  Organization application
> closes
>  March 25th.
>  https://developers.google.com/season-of-docs/docs/timeline
> 
> 
>  thanks,
>  Deepak
> 
> >>>
> >
>
>

Re: New Apache Cassandra Group on LinkedIn

[Patrick McFadin]

I'm not sure if they can merge groups but from what I'm reading that
wouldn't work either. What I'm seeing is a desire to not "promote vendors"
which I believe is working against the project's self-interest. LinkedIn is
the perfect place to do it. The allergic reaction the project has taken for
vendors has made our ecosystem look weak when that's not really the case.
Temporal, Prometheus, Feast, Orkes (to just name a few) all have Cassandra
integrations but you would never know that by looking at any official
Cassandra communication because ecosystem == vendor == bad. The result is
that Cassandra looks like an island that will never help this project grow.

On Wed, Mar 9, 2022 at 9:20 AM Jeremy Hanna 
wrote:

> Is it possible to ask someone at linkedin to merge the groups together so
> that it's managed by the PMC but with the explicit permission of the people
> running the other group?  In the past, I know that Twitter does things like
> that in terms of handles and followers.  Is that a desirable outcome?
>
> On Mar 9, 2022, at 11:00 AM, Benjamin Lerer  wrote:
>
> Hi Patrick,
> Thanks for reaching out. Effectively the discussion has happened between
> the PMC members.
> To explain the context, we wanted to have an official group on Linkedin to
> publish news about the project as we do through the @cassandra handler on
> Twitter. We wanted a group that was vendor independent and focused on
> Apache Cassandra and its ecosystem.
> To be fully transparent, we had no idea that you were in charge of the
> Apache Cassandra Users group as it appears managed by Lynn Bender and
> Joanna Kapel. The group also appears to promote different vendors which is
> something that we wanted to avoid.
> Having to post things under Lynn's name was also an issue for us as we
> wished the merits to go to the right persons.
>
> Now, I am sure that we can work out some solution that will benefit the
> community. :-)
>
> Le mer. 9 mars 2022 à 15:56, Patrick McFadin  a
> écrit :
>
>> I feel like this needs to be a discussion held on the public mailing
>> list. I have been running the Apache Cassandra Users group on LinkedIn for
>> years after taking it over from Lynn Bender.
>> https://www.linkedin.com/groups/3803052/
>>
>> We have over 7500 members and had its ups and downs but it's been pretty
>> consistent as a professional resource on LinkedIn. I'm not sure what there
>> is to gain by creating competing groups. If we need more managers in the
>> group that's fine but somebody just needed to ask. It's clear that this
>> discussion happened somewhere else and this was just an announcement.
>>
>> Patrick
>>
>> On Thu, Mar 3, 2022 at 3:41 AM Benjamin Lerer  wrote:
>>
>>> Hi everybody,
>>>
>>> We just created a new Apache Cassandra group on LinkedIn (
>>> https://www.linkedin.com/groups/9159443/).
>>>
>>> This group will be managed by our community and will respect vendor
>>> neutrality.
>>> Do not hesitate to join and share your experiences or blog posts with us
>>> :-)
>>>
>>
>

Re: New Apache Cassandra Group on LinkedIn

[Jeremy Hanna]

Is it possible to ask someone at linkedin to merge the groups together so that 
it's managed by the PMC but with the explicit permission of the people running 
the other group?  In the past, I know that Twitter does things like that in 
terms of handles and followers.  Is that a desirable outcome?

> On Mar 9, 2022, at 11:00 AM, Benjamin Lerer  wrote:
> 
> Hi Patrick,
> Thanks for reaching out. Effectively the discussion has happened between the 
> PMC members.
> To explain the context, we wanted to have an official group on Linkedin to 
> publish news about the project as we do through the @cassandra handler on 
> Twitter. We wanted a group that was vendor independent and focused on Apache 
> Cassandra and its ecosystem.
> To be fully transparent, we had no idea that you were in charge of the Apache 
> Cassandra Users group as it appears managed by Lynn Bender and Joanna Kapel. 
> The group also appears to promote different vendors which is something that 
> we wanted to avoid.
> Having to post things under Lynn's name was also an issue for us as we wished 
> the merits to go to the right persons.
> 
> Now, I am sure that we can work out some solution that will benefit the 
> community. :-)
> 
> Le mer. 9 mars 2022 à 15:56, Patrick McFadin  > a écrit :
> I feel like this needs to be a discussion held on the public mailing list. I 
> have been running the Apache Cassandra Users group on LinkedIn for years 
> after taking it over from Lynn Bender. 
> https://www.linkedin.com/groups/3803052/ 
> 
> 
> We have over 7500 members and had its ups and downs but it's been pretty 
> consistent as a professional resource on LinkedIn. I'm not sure what there is 
> to gain by creating competing groups. If we need more managers in the group 
> that's fine but somebody just needed to ask. It's clear that this discussion 
> happened somewhere else and this was just an announcement. 
> 
> Patrick
> 
> On Thu, Mar 3, 2022 at 3:41 AM Benjamin Lerer  > wrote:
> Hi everybody,
> 
> We just created a new Apache Cassandra group on LinkedIn 
> (https://www.linkedin.com/groups/9159443/ 
> ).
> 
> This group will be managed by our community and will respect vendor 
> neutrality.
> Do not hesitate to join and share your experiences or blog posts with us :-)

Re: New Apache Cassandra Group on LinkedIn

[Benjamin Lerer]

Hi Patrick,
Thanks for reaching out. Effectively the discussion has happened between
the PMC members.
To explain the context, we wanted to have an official group on Linkedin to
publish news about the project as we do through the @cassandra handler on
Twitter. We wanted a group that was vendor independent and focused on
Apache Cassandra and its ecosystem.
To be fully transparent, we had no idea that you were in charge of the
Apache Cassandra Users group as it appears managed by Lynn Bender and
Joanna Kapel. The group also appears to promote different vendors which is
something that we wanted to avoid.
Having to post things under Lynn's name was also an issue for us as we
wished the merits to go to the right persons.

Now, I am sure that we can work out some solution that will benefit the
community. :-)

Le mer. 9 mars 2022 à 15:56, Patrick McFadin  a écrit :

> I feel like this needs to be a discussion held on the public mailing list.
> I have been running the Apache Cassandra Users group on LinkedIn for years
> after taking it over from Lynn Bender.
> https://www.linkedin.com/groups/3803052/
>
> We have over 7500 members and had its ups and downs but it's been pretty
> consistent as a professional resource on LinkedIn. I'm not sure what there
> is to gain by creating competing groups. If we need more managers in the
> group that's fine but somebody just needed to ask. It's clear that this
> discussion happened somewhere else and this was just an announcement.
>
> Patrick
>
> On Thu, Mar 3, 2022 at 3:41 AM Benjamin Lerer  wrote:
>
>> Hi everybody,
>>
>> We just created a new Apache Cassandra group on LinkedIn (
>> https://www.linkedin.com/groups/9159443/).
>>
>> This group will be managed by our community and will respect vendor
>> neutrality.
>> Do not hesitate to join and share your experiences or blog posts with us
>> :-)
>>
>

Re: GSOD 2022

[Dinesh Joshi]

I looked into the GSoD rules for this year and they have changed significantly. 
Critically, the process requires organizations to collect a list of projects 
and apply to Google for a grant. This includes project ideas, budget and 
metrics for success. If the proposal is accepted Google will issue a grant and 
expect the organizations to select and pay the technical writers. This is a 
significant change from prior years and I don't think, we (Cassandra 
community), are setup for this. We need the ASF to apply as an organization as 
it requires a legal entity to sponsor the whole process including payments. 
This has come up in a separate discussion on comdev so we'll see how it goes. 
As GSoD deadline is March 25, I am not sure if we can participate.

> On Mar 8, 2022, at 5:13 PM, Dinesh Joshi  wrote:
> 
> I haven't looked into GSoD this year. However, the scope of a GSoD project 
> has to be sufficient for the amount of time that is allocated by GSoD. They 
> had 2 project lengths when we last participated - short & long. Projects need 
> to be defined accordingly. It is a lot of work and I personally don't have 
> time to select and mentor the technical writers. I can definitely help guide 
> the application process as I think we also require someone from the PMC to 
> actually submit the application. Nate helped me out when we last participated 
> in GSoD so I'll be happy to help out on that front.
> 
> Here's the page we created for tracking the GSoD Participation and project 
> ideas: 
> https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+GSoD+2019+application
> 
> It would be a good idea to do something similar and get a sense of where our 
> documentation is lacking and then proceed from there.
> 
>> On Mar 8, 2022, at 1:56 PM, Lorina Poland  wrote:
>> 
>> I'm willing to take the lead on GSoD. Let me think about what projects I 
>> think would benefit the docs.
>> 
>> Lorina
>> 
>> On 2022/03/08 16:03:48 Paulo Motta wrote:
>>> Any of the docs contributors interested in taking the lead on this? Perhaps
>>> Dinesh could share some tips on how to create the GSoD application.
>>> 
>>> I think there is a lot of documentation that needs to be created/migrated,
>>> would be nice to have some external help on this.
>>> 
>>> For instance, some virtual tables were added but we have no documentation
>>> on them. Perhaps we could have a GSoD project to better document Virtual
>>> Tables?
>>> 
>>> Em seg., 7 de mar. de 2022 às 17:54, Deepak Vohra 
>>> escreveu:
>>> 
 Has anyone applied for GSOD this year?  Organization application closes
 March 25th.
 https://developers.google.com/season-of-docs/docs/timeline
 
 
 thanks,
 Deepak
 
>>> 
> 

Re: New Apache Cassandra Group on LinkedIn

[Patrick McFadin]

I feel like this needs to be a discussion held on the public mailing list.
I have been running the Apache Cassandra Users group on LinkedIn for years
after taking it over from Lynn Bender.
https://www.linkedin.com/groups/3803052/

We have over 7500 members and had its ups and downs but it's been pretty
consistent as a professional resource on LinkedIn. I'm not sure what there
is to gain by creating competing groups. If we need more managers in the
group that's fine but somebody just needed to ask. It's clear that this
discussion happened somewhere else and this was just an announcement.

Patrick

On Thu, Mar 3, 2022 at 3:41 AM Benjamin Lerer  wrote:

> Hi everybody,
>
> We just created a new Apache Cassandra group on LinkedIn (
> https://www.linkedin.com/groups/9159443/).
>
> This group will be managed by our community and will respect vendor
> neutrality.
> Do not hesitate to join and share your experiences or blog posts with us
> :-)
>

Re: [DISCUSS] Next release cut

[Benjamin Lerer]

>
> We also have the requirement that there will be no release without green
> CI. Do we cut a release branch on the 1st May if we don't yet have a green
> CI and can't be making a cut off it?


I would propose to create the new branch on the 1st of May and consider it
feature freeze. We can then look at its state. If we have minor issues, fix
them otherwise rollback the problematic changes.
Having a green CI should be our priority today as it will allow us to
minimize the risk of introducing new issues as we progress toward the
release.

Le mer. 9 mars 2022 à 01:20, Ekaterina Dimitrova  a
écrit :

> I tend to agree with Mick. We should have a bit of time to look around and
> do a final cross check. Also, our CI is really painful these days and I am
> not talking only about test failures, but infra.
>
> On Tue, 8 Mar 2022 at 13:56, Mick Semb Wever  wrote:
>
>> We do not want to encourage/enable the rush to commit stuff before the
>>> 1st May cut-off. IMHO we should be comfortable leaning towards saving any
>>> significant commits for the next dev cycle.
>>>
>>> With sufficient testing added for a new feature, feature flags for
>>> optionality, and a window of time to fuzz test things, why should we shy
>>> away from even large commits the day before we freeze if they have a green
>>> CI board?
>>>
>>
>>
>> Yes, we are aligned here. If things are done properly then that's not "a
>> rush", and there's no reason we shouldn't be _working as normal_ up until
>> the 1st May. Keeping in mind that the time to do it properly can be
>> something out of your control: CI not working, rebasing if there's a lot
>> landing in trunk, etc.
>>
>> We also have the requirement that there will be no release without green
>> CI. Do we cut a release branch on the 1st May if we don't yet have a green
>> CI and can't be making a cut off it?
>>
>>