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 assignm
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!
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 pag
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
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
ven
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?
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 indep
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
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 pr
>
> 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 l
10 matches
Mail list logo
