The CQL spec for COUNT says:
"It also can be used to count the non null value of a given column. Example:
SELECT COUNT(scores) FROM plays;"
But, the parser only recognizes COUNT(*) and COUNT(1).
See:
https://cassandra.apache.org/doc/cql3/CQL-3.0.html
https://github.com/apache/cassandra/blob/tru
May be I misunderstood you.
Do you mean that you tested it and that it is not working on the version
you used?
On Mon, Apr 18, 2016 at 3:50 PM, Jack Krupansky
wrote:
> The CQL spec for COUNT says:
>
> "It also can be used to count the non null value of a given column.
> Example:
>
> SELECT COUNT
Hi Jack,
You are looking at the wrong place. count() is a native
function. There nothing specific for it in the parser syntax.
Benjamin
On Mon, Apr 18, 2016 at 3:50 PM, Jack Krupansky
wrote:
> The CQL spec for COUNT says:
>
> "It also can be used to count the non null value of a given column.
No, I didn't test, I was just reading the code, but I hadn't checked for
all occurrences of K_COUNT, so I hadn't noticed that it also occurs in the
allowedFunctionName grammar production rule. And I found the code that
dynamically creates a count function for each type here:
https://github.com/apac
Apache Cassandra Support,
In order to install this software on our servers, I need help from Planet
Cassandra in completing the attached questionnaire for Northrop Grumman
Information Security. Please provide as much detail as possible for all
questions. If you have any questions for me, plea
Here's a recent security assessment discussion - list of questions,
proposed response, and discussion, which you might find helpful, courtesy
of Oleg Yusim:
https://docs.google.com/document/d/13-yu-1a0MMkBiJFPNkYoTd1Hzed9tgKltWi6hFLZbsk/edit?ts=56c3a130#heading=h.xq6exsjcda8
-- Jack Krupansky
On
Hi All,
For last several months, the "most stable version" question pops up on the user
mailing list and then people get all sorts of responses/suggestions..
If you are conservative go for x if adventurous y..
If you have good risk appetite go for x else y..
If you want features go for x else y..
This is best for the users list. Test the releases yourself and then decide
when it's ready for your use case, ops team, and organization. This is a
personal decision and not one for *thousands* of others on this mailing list to
make for you.
best,
kjellman
> On Apr 18, 2016, at 10:54 AM, Anuj
I am sorry but here, I am not expecting thousands to decide a stable version
for my use case. I have a serious question about publishing some info on the
Apache website. As dev list has active contributors, I posted it here. If not
this forum, Whats the best way to put your suggestions regarding
Just a heads up that I've sent out acceptances for 52 people. If you're
surprised that you didn't get one, please resubmit your information.
Also, that leaves us with room for about ten more, so if you were on the
fence about coming, go for it!
On Thu, Mar 10, 2016 at 10:22 PM, Jonathan Ellis w
My blog post regarding this:
https://www.pythian.com/blog/cassandra-version-production/
There is a choice for everyone, and explained.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your data
rolo@pythian | Twitter: @cjrolo | Li
Hi All,
Let me reiterate, my question is not about selecting right Cassandra for me.
The intent is to get dev community response on below question.
Question:
Would it be a wise decision to mention the "most stable/production
ready" version (as it used to be before 3.x) on the Apache website till
t
Anuj,
The problem is that this question defies a simplistic answer like "version
X is the most stable" (are you willing to use unsupported releases? what
about emergency-fix-only? what features can you not live without?) so
we're intentionally resisting the urge to oversimplify the situation.
O
13 matches
Mail list logo
