Re: Opinions about removal of deprecated code for upcoming 4.0

A lot of those methods if I am not wrong have been marked as deprecated in 4.0. So they should not be removed yet, as Jeff mentioned. The problem I see is that those deprecations have not been mentioned in the deprecation section of the NEWS.txt. As they are MBeans methods, unless people have che

Re: Discussion: addition to CEP guide

+1 for both On Thu, Apr 23, 2020 at 3:49 AM Jordan West wrote: > +1 (nb) on both counts. Thanks for bringing this up! > > Jordan > > On Wed, Apr 22, 2020 at 11:53 AM Joshua McKenzie > wrote: > > > > > > > Maybe put it high up the list, e.g. after Description of Approach? > > > > Really great

Re: Using a user defined type in user defined aggregate

Hi Andrea, Question 1) When I call the aggregate, I would like to pass sample_size > with a sub-query, e.g. > ==> "SELECT bloomfilter_uda(name, (SELECT count(*) FROM test_table)) > FROM test_table;" <== > Is that possible with Cassandra? Sub queries are not supported by Cassandra. Question 2) W

Re: [DISCUSSION] Flaky tests

> > Most of these were fixed in CASSANDRA-15622 > But the remaining failures are from the use of > `FBUtilities.getLocalAddress()` and `InetAddress.getLocalHost()`. It > affects ci-cassandra because the agents need their public ip so the > master can reach them. > > Some help with how best to fix t

Re: [DISCUSS] Considering when to push tickets out of 4.0

Just to clarify the status of CASSANDRA-14825 The latest version of the patch has been reviewed by Dinesh and I. I am fixing the last details (mainly the documentation). So I expect the patch to be ready to commit, today or tomorrow. On Wed, Jun 17, 2020 at 10:36 AM Benedict Elliott Smith wrote:

Re: [VOTE] Project governance wiki doc

+1 (binding) On Wed, Jun 17, 2020 at 12:49 PM Marcus Eriksson wrote: > +1 > > > On 17 June 2020 at 12:40:38, Sam Tunnicliffe (s...@beobal.com) wrote: > > +1 (binding) > > > > > On 17 Jun 2020, at 09:11, Jorge Bay Gondra wrote: > > > > > > +1 nb > > > > > > On Wed, Jun 17, 2020 at 7:41 AM Mick Se

Re: [VOTE] Project governance wiki doc (take 2)

+1 On Mon, Jun 22, 2020 at 8:54 AM Marcus Eriksson wrote: > +1 > > > On 22 June 2020 at 08:37:39, Mick Semb Wever (m...@apache.org) wrote: > > > - Vote will run through 6/24/20 > > - pmc votes considered binding > > - simple majority of binding participants passes the vote > > - committer and co

Re: [DISCUSS] When to branch 4.0

I believe that we all need to see 4.0.0 being released. We have been frozen for too long in my opinions and some people simply believe that the project is dead. That is hurting us. That does not mean that I am not in favor of making that release as stable as possible. What we miss in my opinion is

Re: [DISCUSS] When to branch 4.0

al to > the organisation, and shape their actions in turn. If there is a > disconnect between the implied and expressed priorities, this leads to > tensions; usually to the detriment of the expressed priorities, since > actions speak louder than words. > > > On 29/06/2020, 10

Re: [DISCUSS] When to branch 4.0

gests I have assumed any negative intentions? > Sometimes this phrase reads as a thought-terminating cliché. > > > > On 29/06/2020, 13:28, "Benjamin Lerer" > wrote: > > > > > If this is in response to my email, you misunderstand me. > > >

Re: [DISCUSS] When to branch 4.0

bout 5.0 or a roadmap for it. If we want to talk about > that let's take it to another thread. > > Also, this thread wasn't intended to discuss what our bar of quality for a > release of 4.0 should be. I think that's a great topic. Let's take that to > another t

Re: [DISCUSS] Stabilizing 4.0

Thanks a lot for starting this thread Dinesh. As a baseline expectation, we thought big users of Cassandra should be > running the latest trunk internally and testing it out for their particular > use cases. We wanted them to file as many jiras as possible based on their > experience. Operations s

Re: [DISCUSS] Stabilizing 4.0

om.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report&atl_token=A5KQ-2QAV-T4JA-FDED_fd75a3db98350d94229fbb4cf29cb50f3051d7ce_lin&Next=Next On Tue, Jun 30, 2020 at 10:20 AM Benjamin Lerer wrote: > Thanks a lot for starting this thread Dinesh. > > As a baseline expectat

Re: [DISCUSS] Stabilizing 4.0

It is a good catch, Mick. :-) I will triage those tickets to be sure that our view of things is accurate. On Tue, Jun 30, 2020 at 11:38 AM Berenguer Blasi wrote: > That's a very good point. At the risk of saying sthg silly or being > captain obvious, as I am not familiar with the project dynam

Re: [DISCUSS] Future of MVs

> > "Make the scan faster" > "Make the scan incremental and automatic" > "Make it not blow up your page cache" > "Make losing your base replicas less likely". > > There's a concrete, real opportunity with MVs to create integrity > assertions we're missing. A dangling record from an MV that would po

Re: naming development branches consistently

+1 for trunk or main (slight preference for trunk) On Tue, Aug 25, 2020 at 8:52 PM Mick Semb Wever wrote: > +1 for trunk and main. > > Thanks for raising this Brandon. > > > > On Tue, 25 Aug 2020 at 20:40, Cyril Scetbon wrote: > > > Scott, I don’t think it does and don’t see any offense in wh

Re: [VOTE] Release Apache Cassandra 4.0-beta2

+1 On Mon, Aug 31, 2020 at 7:42 AM Marcus Eriksson wrote: > +1 > > > On 28 August 2020 at 16:19:36, Mick Semb Wever (m...@apache.org) wrote: > > Proposing the test build of Cassandra 4.0-beta2 for release. > > > > sha1: 56eadf2004399a80f0733041cacf03839832249a > > Git: > > > https://gitbox.apa

Re: [VOTE] Release Apache Cassandra 2.2.18

+1 On Mon, Aug 31, 2020 at 7:43 AM Marcus Eriksson wrote: > +1 > > > On 28 August 2020 at 14:45:08, Mick Semb Wever (m...@apache.org) wrote: > > Proposing the test build of Cassandra 2.2.18 for release. > > > > sha1: d4938cf4e488a9ef3ac48164a3e946f16255d721 > > Git: > > > https://gitbox.apache

Re: [VOTE] Release Apache Cassandra 3.0.22

+1 On Mon, Aug 31, 2020 at 7:43 AM Marcus Eriksson wrote: > +1 > > > On 28 August 2020 at 15:09:53, Mick Semb Wever (m...@apache.org) wrote: > > Proposing the test build of Cassandra 3.0.22 for release. > > > > sha1: 45331bb612dc7847efece7e26cdd0b376bd11249 > > Git: > > > https://gitbox.apache.

Re: [VOTE] Release Apache Cassandra 3.11.8

+1 On Mon, Aug 31, 2020 at 9:15 AM Tommy Stendahl wrote: > +1 NB > > On fre, 2020-08-28 at 15:37 +0200, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.11.8 for release. > > sha1: 8b29b698630960a0ebb2c695cc5b21dee4686d09 > Git: > > https://gitbox.apache.org/repos/asf?p=cassa

Re: [VOTE] Release Apache Cassandra 2.1.22

+1 On Fri, Aug 28, 2020 at 7:27 PM Brandon Williams wrote: > +1 > > On Fri, Aug 28, 2020 at 10:43 AM Mick Semb Wever wrote: > > > > Proposing the test build of Cassandra 2.1.22 for release. > > > > sha1: 94e9149c22f6a7772c0015e1b1ef2e2961155c0a > > Git: > > > https://gitbox.apache.org/repos/

Re: Problem in updating schema in Cassandra 3.11.4

Hi, Could you precise what you mean by " will only validate the schema while changing in memory, and will not validate before flush to disk.". It is unclear to me of which validation you are talking about. On Tue, Sep 1, 2020 at 1:44 PM Weiliang Zhang <394693...@qq.com> wrote: > Does anyone

Re: [DISCUSS] Change style guide to recommend use of @Override

+1 On Wed, Sep 2, 2020 at 5:36 AM Berenguer Blasi wrote: > +1 > > On 2/9/20 5:09, Joshua McKenzie wrote: > > +1 > > > > On Tue, Sep 1, 2020 at 6:26 PM Jordan West wrote: > > > >> +1 > >> > >> On Tue, Sep 1, 2020 at 12:22 PM Benedict Elliott Smith < > >> bened...@apache.org> > >> wrote: > >> >

Re: Creating a branch for 5.0 …?

> > People might be itching to get out, particularly those who are unlikely to > be harmed, but most agree to stay put for the benefit of the community. > The freeze has been there for quite a while now and as far as I can see the goal of all those working on C* right now is to have 4.0 out. Will

Re: [VOTE] Accept the Harry donation

+1 On Wed, Sep 16, 2020 at 12:00 PM Mick Semb Wever wrote: > > Please cast your votes: > >[ ] +1 Accept the contribution into Cassandra > >[ ] -1 Do not > > > > > +1 >

Re: [DISCUSS] Next steps for Kubernetes operator SIG

> > I realise there are meeting logs, but getting a wider discourse with > non-stakeholder input might help to build a community consensus? It > doesn't seem like it can hurt at this point, anyway. > +1 On Wed, Sep 23, 2020 at 9:21 PM Benedict Elliott Smith wrote: > Perhaps it helps to widen

Re: [VOTE] Release Apache Cassandra 3.0.23

+1 On Mon, Nov 2, 2020 at 7:25 AM Tommy Stendahl wrote: > +1 (nb) > > On Thu, 2020-10-29 at 13:28 +0100, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.0.23 for release. > > > > sha1: 31530ff5ac6bd3bacd4b378573a2d191bdab8cd7 > > Git: > > > https://gitbox.apache.org/repos/as

Re: [VOTE] Release Apache Cassandra 4.0-beta3

+1 On Sun, Nov 1, 2020 at 2:49 AM Yuji Ito wrote: > +1 (non-binding) > > Short Jepsen tests passed. > https://github.com/scalar-labs/scalar-jepsen > > 2020年11月1日(日) 10:23 Yifan Cai : > > > +1 nb > > > > > > From: Scott Andreas > > Sent: Saturday, October 31,

Re: [VOTE] Release Apache Cassandra 3.11.9

+1 On Mon, Nov 2, 2020 at 7:25 AM Tommy Stendahl wrote: > +1 nb > > On Thu, 2020-10-29 at 13:29 +0100, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.11.9 for release. > > > > sha1: 5ef75dd96cb693e4041e9ecb61a6852276f0eca4 > > Git: > > > https://gitbox.apache.org/repos/asf

[DISCUSS] CASSANDRA-12126: LWTs correcteness and performance

CASSANDRA-12126 addresses one correctness issue of Light Weight Transactions. Unfortunately, the current patch developed by Sylvain and Benedict requires an extra round trip between the coordinator and the replicas for SERIAL and LOCAL_SERIAL reads. After some experimentations, Benedict discovered

Re: [DISCUSS] CASSANDRA-12126: LWTs correcteness and performance

I will try to summarize the discussion to clarify the outcome. Mick is in favor of #4 Summanth is in favor of #4 Sylvain answer was not clear for me. I understood it like I prefer #3 to #4 and I am also fine with #1 Jeff is in favor of #3 and will understand #4 David is in favor #3 (fix bug and ad

Re: [DISCUSS] CASSANDRA-12126: LWTs correcteness and performance

Smith < > bened...@apache.org> wrote: > > > > Well, I expressed a preference for #3 over #4, particularly for the > 3.x series. However at this point, I think the lack of a clear project > decision means we can punt it back to you and Sylvain to make the fina

Re: [DISCUSS] CASSANDRA-12126: LWTs correcteness and performance

Paulo, what you propose with the yaml seems different from default to *correctness*. It means to me that we are forcing the user to choose between *correctness *and *performance*. Most of us have a good understanding of the problem and it is a hard choice for us. I imagine that most of the users do

Re: [DISCUSS] CASSANDRA-12126: LWTs correcteness and performance

rt article about the options and the tradeoffs, further > to > > NEWS.txt (that’s not something to decide now, of course :-) ) > > > > > > On Tue, 24 Nov 2020 at 9:13, Benjamin Lerer > > > wrote: > > > > > Paulo, what you propose with the yaml seems dif

Re: [VOTE] Release dtest-api 0.0.7

+1 On Thu, Dec 3, 2020 at 7:23 PM David Capwell wrote: > +1 > > > On Dec 3, 2020, at 10:20 AM, Scott Andreas wrote: > > > > +1nb > > > > > > From: Brandon Williams > > Sent: Thursday, December 3, 2020 10:05 AM > > To: dev@cassandra.apache.org > > Subjec

Which fix version should be used for the Quality Testing tickets

Hi everybody, Looking at the Dashboard, it seems that the *Quality Testing* tickets are spread between the Beta and RC releases. https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661 I assumed that those tickets were part of the Beta release but I might have misunde

Re: Which fix version should be used for the Quality Testing tickets

It looks like my question raised more questions than I had in mind. 1. What is the meaning of the fix version? 2. When do we move from beta to RC? 3. Where does the Quality tickets fit in all that? *What is the meaning of the fix version?* It looks like we should just pick a definition and docu

Re: Which fix version should be used for the Quality Testing tickets

changed > >> features with modest testing): Block RC > >> - Anticipated not to find serious bugs (e.g. old unchanged but poorly > >> tested features): Block GA > >> > >> Which mostly accords with what you're saying re: today's state of play I &

Re: Which fix version should be used for the Quality Testing tickets

of scope of those tasks, if we anticipate release dragging on > too much longer. > > > On 11/12/2020, 17:07, "Benjamin Lerer" > wrote: > > > > > As an aside, I disagree about this blocking GA. We have a decade or > so of > > debt and this is

Re: Triggers

Hi Greg, Things are more tricky in an eventually consistent distributed system than they are in a relational database. Even if the C* triggers were perfect (and they are not) and your write and read tables were exactly the same, there is no guarantee that all the updates created by the trigger fro

Welcome Jordan West, David Capwell, Zhao Yang and Ekaterina Dimitrova as Cassandra committers

The PMC's members are pleased to announce that Jordan West, David Capwell, Zhao Yang and Ekaterina Dimitrova have accepted the invitations to become committers this year. Jordan West accepted the invitation in April David Capwell accepted the invitation in July Zhao Yang accepted the invitation in

Re: Which fix version should be used for the Quality Testing tickets

Thanks Mick for raising that problem. Effectively, I got confused along the way. +1 On Thu, Dec 17, 2020 at 11:56 AM Sam Tunnicliffe wrote: > > > > On 17 Dec 2020, at 10:54, Michael Semb Wever wrote: > > > > > >> I propose to: > >> > >> - update the documentation to clarify the meaning of th

Re: Regarding Materialized Views

Hi Shaurya, 1. When will MVs be enabled for production use again ? > It is difficult to give an exact target but as Zhao pointed out it is in our radar for after 4.0 On Fri, Dec 18, 2020 at 10:50 AM Jasonstack Zhao Yang < jasonstack.z...@gmail.com> wrote: > Hi, > > > 1. When will MVs be enabl

Re: Regarding Materialized Views

8, 2020 at 3:30 PM Benjamin Lerer < > benjamin.le...@datastax.com> > wrote: > > > Hi Shaurya, > > > > 1. When will MVs be enabled for production use again ? > > > > > > > It is difficult to give an exact target but as Zhao pointed out it is in >

Welcome Yifan Cai as Cassandra committer

The PMC's members are pleased to announce that Yifan Cai has accepted the invitation to become committer last Friday. Thanks a lot, Yifan, for everything you have done! Congratulations and welcome The Apache Cassandra PMC members

[DISCUSS] Revisiting the quality testing epic scope

Hi everybody, As discussed before the holidays, it might make sense to revisit the scope of the quality testing tickets for 4.0 GA to ensure that the 4.0 release is not held for longer than necessary. The current status of the quality testing tasks are the following: *DONE:* * CASSANDRA-15583 <

Re: [DISCUSS] Revisiting the quality testing epic scope

PoolTest.testPromptnessOfExecution > – CASSANDRA-16358: Minor Flakiness in > ProxyHandlerConnectionsTest#testExpireSomeFromBatch > – CASSANDRA-16229: Flaky jvm-dtest: > org.apache.cassandra.distributed.test.ring.NodeNotInRingTest.nodeNotInRingTest > – CASSANDRA-16061: > transient_replication_ring_test.py::TestTransie

Re: [DISCUSS] Removal of third-party plug-ins doc page

+1 On Thu, Jan 21, 2021 at 10:58 AM Michael Semb Wever wrote: > > > Should this page be removed from at least the Cassandra 4.0 > documentation? > > Neither seems to have been updated beyond C* 3.0. > > > Good idea Lorina. Do please remove it. > > We have now https://cassandra.apache.org/thir

Re: [DISCUSS] When to stop supporting Python 2

We have a check in CQLSH that prevents it to start if the python version is lower than python 2.7. I am fine dropping support for python 2 as long as we make it explicits in the NEWS.txt and that we add a warning in CQLSH to notify python 2 users that it is not supported anymore and might not work

Re: [DISCUSS] When to stop supporting Python 2

e when upgrading and what is the expected cost of keeping support for 2.7 until the next major? On Tue, Jan 26, 2021 at 10:39 AM Benjamin Lerer wrote: > We have a check in CQLSH that prevents it to start if the python version > is lower than python 2.7. I am fine dropping support for python 2

Re: [DISCUSS] When to stop supporting Python 2

have more visibility on this point before deciding about our approach for python 2. I will fire a thread to discuss the plan for the future major release. On Tue, Jan 26, 2021 at 11:02 AM Benjamin Lerer wrote: > According to some study I found here > <https://www.activestate.com/resour

[DISCUSS] Releases after 4.0

Hi everybody It seems that there is a need to discuss how we will deal with releases after 4.0 We are now relatively close from the 4.0 RC release so it make sense to me to start discussing that subject especially as it has some impact on some things like dropping support for python 2 The main q

Re: [DISCUSS] Releases after 4.0

ather than behind - this might also alleviate > pressure for hitting release windows with features. > > > > > On 26/01/2021, 13:56, "Benjamin Lerer" > wrote: > > Hi everybody > > It seems that there is a need to discuss how we will deal

Re: [DISCUSS] When to stop supporting Python 2

Considering the issue with pip. I agree that we should remove support for 3.0 and ensure that python 3 is supported by 3.11. On Wed, Jan 27, 2021 at 8:18 PM Jonathan Ellis wrote: > Python 2 was EOLed over a year ago. I think it's fine to (1) require > python 3 to run cqlsh and (2) remove code t

Re: [DISCUSS] Releases after 4.0

I am a bit scared of a continuous delivery approach for a database due to the lack of guarantee on the APIs and protocols as you mentioned. On the other hand an annual major release cadence seems a bit too inflexible for me. It makes sense to me to ensure that we release at least one major version

Re: [VOTE] Release Apache Cassandra 3.11.10

+1 On Mon, Feb 1, 2021 at 10:25 AM Tommy Stendahl wrote: > +1 (nb) > > On Fri, 2021-01-29 at 13:50 +0100, Oleksandr Petrov wrote: > > Proposing the test build of Cassandra 3.11.10 for release. > > > > sha1: 181a4969290f1c756089b2993a638fe403bc1314 > > Git: > > > > https://gitbox.apache.org/rep

Re: [VOTE] Release Apache Cassandra 3.0.24

+1 On Mon, Feb 1, 2021 at 9:08 AM Marcus Eriksson wrote: > +1 > > On Fri, Jan 29, 2021 at 01:48:22PM +0100, Oleksandr Petrov wrote: > > Proposing the test build of Cassandra 4.0-beta4 for release. > > > > sha1: 6748ecd63cae047b5b0e8c3165088252954e9d5f > > Git: > > > https://gitbox.apache.org/

Re: Pushing CASSANDRA-16262 out of 4.0-rc

It seems to me that CASSANDRA-16180 , CASSANDRA-16262 and CASSANDRA-16181 already highly improve the test coverage on distributed re

Re: [DISCUSS] Releases after 4.0

Thanks for your responses. I had some offline discussions with different persons to gather more feedback on the current discussion. The people I talked to appeared to be in favor of one supported release every year as Benedict initially suggested. The advantages mentioned were: * it is long enough

Re: [DISCUSS] Releases after 4.0

> > Are we also trying to reach a consensus here that a release branch should > be supported for ~3 years (i.e. that we are aiming to limit ourselves to 3 > release branches plus trunk)? 3 release branches make sense to me +1 On Fri, Feb 5, 2021 at 6:15 PM Michael Semb Wever wrote: > > > I b

Welcome Paulo Motta as Cassandra PMC member

The PMC's members are pleased to announce that Paulo Motta has accepted the invitation to become a PMC member yesterday. Thanks a lot, Paulo, for everything you have done for the project all these years. Congratulations and welcome The Apache Cassandra PMC members

Re: Pushing CASSANDRA-16262 out of 4.0-rc

e frequently. > > Maybe it's ok to release a release candidate, but we probably should still > wait a bit to cut a final release. WDYT? > > > > > On Mon, Feb 1, 2021 at 1:33 PM Benjamin Lerer > > wrote: > > > It seems to me that CASSANDRA-16180 > > &

Re: New Cassandra website for review

A huge thanks to everybody that contributed to the new website. All your efforts have paid off. That is truly an amazing work! Le lun. 1 mars 2021 à 03:08, Ben Bromhead a écrit : > Awesome stuff, looks great! > > On Mon, Mar 1, 2021 at 9:33 AM Nate McCall wrote: > > > Thanks Melissa! This look

Re: Project Roadmap

> > I think of a roadmap as a pre-CEP activity for upcoming releases, items > thereon beginning the CEP process, with target releases being assigned by > the roadmap (subject to revision) and project members opting-in to the > endeavour to deliver for that release. I am a bit confused by that par

Re: Project Roadmap

Having an open discussion about what we want to release as a community on the next version makes total sense to me. I also agree that the roadmap should not be written on stone and that we should be flexible if we believe that we need to. We should also take this discussion as an opportunity to dis

Re: Project Roadmap

t; make explicit trade-offs as a community about what we want to invest in > before the next release. > > > > > > On 01/03/2021, 13:26, "Benjamin Lerer" wrote: > > > > Having an open discussion about what we want to release as a > community on > >

Re: Project website analytics

Thanks a lot to Stefan, Mick and Instaclustr. :-) On Wed, Mar 10, 2021 at 2:28 PM Mick Semb Wever wrote: > > > > > > The box this service runs at is donated by Instaclustr, we are glad to > > help! > > > > > This is really awesome of you, Stefan and Instaclustr. Thanks! >

Wiki

Hi, Could you add me to the *Contributors* with permission to edit the Cassandra wiki? My username is BenjaminLerer. Thanks a lot, Benjamin

Re: Wiki

Thanks [image: datastax_logo.png] <http://www.datastax.com/> Benjamin Lerer Software Engineer| +41 76 396 64 60 | benjamin.le...@datastax.com [image: linkedin.png] <http://ch.linkedin.com/pub/benjamin-lerer/2/303/784/> [image: facebook.png] <https://www.facebook.com/d

Re: Should we make everything blue in Jenkins?

. [image: datastax_logo.png] <http://www.datastax.com/> Benjamin Lerer Software Engineer| +41 76 396 64 60 | benjamin.le...@datastax.com [image: linkedin.png] <http://ch.linkedin.com/pub/benjamin-lerer/2/303/784/> [image: facebook.png] <https://www.facebook.com/datastax> [image: t

Re: [VOTE] Release Apache Cassandra 3.0.0-beta1

+1 [image: datastax_logo.png] <http://www.datastax.com/> Benjamin Lerer Software Engineer| +41 76 396 64 60 | benjamin.le...@datastax.com [image: linkedin.png] <http://ch.linkedin.com/pub/benjamin-lerer/2/303/784/> [image: facebook.png] <https://www.facebook.com/datastax> [

Re: [VOTE] Release Apache Cassandra 3.0.0-rc1

debian package are also available here: > http://people.apache.org/~jake > > The vote will be open for 24 hours (longer if needed). > > [1]: http://goo.gl/m3OPOV (CHANGES.txt) > [2]: http://goo.gl/Z0HNhw (NEWS.txt) > -- [image: datastax_logo.png] <http://www.data

Re: Is it possible to group by timestamp in hour, day, weeks.. in Cassandra?

oup by within Materialized View ( CASSANDRA-9778) <https://issues.apache.org/jira/browse/CASSANDRA-9778> [image: datastax_logo.png] <http://www.datastax.com/> Benjamin Lerer Software Engineer| +41 76 396 64 60 | benjamin.le...@datastax.com [image: linkedin.png] <http://ch.linkedin.com

Re: [VOTE] Release Apache Cassandra 3.1

+1 On Friday, December 4, 2015, Jake Luciani wrote: > I propose the following artifacts for release as 3.1. > > sha1: e092873728dc88aebc6ee10153b9bd3cd90cd858 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.1-tentative > Artifacts: > > https://repositor

Re: [VOTE] Release Apache Cassandra 3.0.1

+1 On Friday, December 4, 2015, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.1. > > sha1: cf567703db2cc6859731405322f19f55345b5c57 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.1-tentative > Artifacts: > > https://repos

Re: [VOTE] Release Apache Cassandra 3.1.1

+1 On Thu, Dec 17, 2015 at 8:40 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.1.1. > > sha1: 8347d37716d318956591ab7d5688774a083e5bfb > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.1.1-tentative > Artifacts: > > https://r

Re: [VOTE] Release Apache Cassandra 3.0.2

+1 On Thu, Dec 17, 2015 at 8:42 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.2. > > sha1: 9b655ac181e732e2c489e102d6742cad6f7029e6 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.2-tentative > Artifacts: > > https://r

Re: Proposal: deprecate Thrift now and remove support in 4.0

+1 On Mon, Dec 28, 2015 at 4:50 PM, Josh McKenzie wrote: > +1 > > On Mon, Dec 28, 2015 at 9:26 AM, Jonathan Ellis wrote: > > > Thrift has been officially frozen for almost two years and unofficially > for > > longer. [1] Meanwhile, maintaining Thrift support through changes like > > 8099 has b

Re: TTL support in String Boot Application

Hi Kiran, This mailing list is for questions about Cassandra development only and your problem is clearly coming from the springframework, not from Cassandra. Benjamin On Tue, Dec 29, 2015 at 6:53 AM, Kiran Singh wrote: > Hello, > > I am trying to write a simple spring boot application, which

Re: Release date for 2.1.13

Hi, The vote should start end of next week. Benjamin On Thu, Jan 28, 2016 at 10:38 PM, Viru Kanjilal wrote: > Hello > > Does anyone know the expected release date for 2.1.13? > > Thanks > Viru >

Re: Issue with pagination and IN clause

Thanks for reporting the problem. I will look into it. Regards, Benjamin On Sun, Feb 21, 2016 at 3:19 PM, Luis Ángel Vicente Sánchez < langel.gro...@gmail.com> wrote: > I think I have found an issue when you have a simple column family with a > simple primary key (no clustering keys) and you us

Re: Issue with pagination and IN clause

(1, 2, 3); -- Wrong > PAGING 2; > SELECT * FROM test WHERE pk IN (1, 2, 3); -- Wrong > > The output of the last query is: > > pk | rc > + > 1 | 1 > 2 | 2 > > ---MORE--- > pk | rc > + > 2 | 2 > 3 | 3 > > ---MORE--- >

Re: [VOTE] Release Apache Cassandra 3.4

+1 On Sat, Mar 5, 2016 at 2:43 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.4. > > sha1: 70649a8d65825144fcdbde136d9b6354ef1fb911 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.4-tentative > Artifacts: > > https://reposi

Re: [VOTE] Release Apache Cassandra 3.0.4

+1 On Sat, Mar 5, 2016 at 2:46 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.4. > > sha1: 6328590808ff16fd026fd80cb28635d4313b8cc8 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.4-tentative > Artifacts: > > https://re

Re: How to measure the write amplification of C*?

Cassandra should not cause any write amplification. Write amplification appends only when you updates data on SSDs. Cassandra does not update any data in place. Data can be rewritten during compaction but it is never updated. Benjamin On Thu, Mar 10, 2016 at 12:42 PM, Alain RODRIGUEZ wrote: > H

Re: [VOTE] Release Apache Cassandra 3.0.5

+1 On Fri, Apr 8, 2016 at 12:10 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.5. > > sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative > Artifacts: > > https://r

Re: Typo in CommitLog.java: maxiumum s.b. maximum

Hi Jack, Thanks for reporting the problem. I will fix it. Benjamin On Sun, Apr 10, 2016 at 10:10 PM, Jack Krupansky wrote: > I was baffled why I couldn't find a user's reported log message of > "Mutation 32MB too large for maximum size of 16Mb" even when I searched > GitHub for "too large for

Re: [VOTE] Release Apache Cassandra 3.5 (Attempt #2)

+1 On Sun, Apr 10, 2016 at 5:43 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.5. > > sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative > Artifacts: > > https://repos

Re: CQL spec error: COUNT(column)

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

Re: CQL spec error: COUNT(column)

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.

Re: Typo in comment for maxFunctionForCounter in AggregateFcts.java

I will fix it. I am the one that has probably done them anyway. Benjamin On Tue, Apr 19, 2016 at 4:57 PM, Jack Krupansky wrote: > Comment typo for maxFunctionForCounter in AggregateFcts.java: > > /** > * AVG function for counter column values. > */ > public static final Aggreg

Re: Typo in comment for maxFunctionForCounter in AggregateFcts.java

Done. Thanks for reporting the problem. On Tuesday, April 19, 2016, Benjamin Lerer wrote: > I will fix it. I am the one that has probably done them anyway. > > Benjamin > > On Tue, Apr 19, 2016 at 4:57 PM, Jack Krupansky > wrote: > >> Comment typo f

Re: [VOTE] Release Apache Cassandra 3.0.6

+1 On Wed, May 11, 2016 at 9:44 AM, Sylvain Lebresne wrote: > +1 > > On Wed, May 11, 2016 at 6:23 AM, Jonathan Ellis wrote: > > > +1 > > > > On Tue, May 10, 2016 at 8:54 PM, Jake Luciani wrote: > > > > > I propose the following artifacts for release as 3.0.6. > > > > > > sha1: 52447873a361647a

Re: [VOTE] Release Apache Cassandra 3.6

+1 On Wed, May 11, 2016 at 11:15 AM, Sam Tunnicliffe wrote: > +1 > > On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko > wrote: > > > +1 > > > > -- > > AY > > > > On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote: > > > > I propose the following artifacts for release as 3.6. > >

Re: [VOTE] Release Apache Cassandra 3.6 (Attempt #2)

+1 On Wed, Jun 1, 2016 at 7:30 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.6. > > sha1: 8d22d9fd1842c59ea65a3793aceb5a78c5852351 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative > Artifacts: > > https://reposi

Re: NewBie Question ~ Book for Cassandra

Hi Chris, Disclaimer: I am a Datastax employee It is clear to me that the current official documentation is far from being enough. That's why I fully support the decision made by Jonathan to do our best to improve it. As an Apache Cassandra Committer mostly working on the CQL layer, I know that

Re: NewBie Question ~ Book for Cassandra

r more than the basics. On Mon, Jun 13, 2016 at 3:05 PM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > Hi Benjamin, > > > > On 6/13/16, 6:38 AM, "Benjamin Lerer" wrote: > > >Hi Chris, > > > >Disclaimer: I am a Datastax e

Re: Help requested: o.a.c.cql3.validation unit tests periodically hang

o.a.c.cql3.validation contains a lot of tests. Most of them are not real unittest in the sense that they start and use a C* server. I am not sure of how it is done but if we ran multiple tests in parallel we have to be carefull that those test do not interfer with each others. For example, some tes

Re: restrictions on IN operator

Since 2.2, IN restrictions are supported on any partition key or clustering colum in SELECT statement. For UPDATE and DELETE statement they are supported since 3.0. Benjamin On Tue, Sep 6, 2016 at 11:19 AM, Samba wrote: > Hi, > > I understand, from the documentation, that IN operator is permitt

Re: OOM with one query.

Thanks for reporting the problem. Could you open a JIRA ticket. I will look into it. Benjamin On Tue, Sep 6, 2016 at 4:08 PM, Eduardo Alonso wrote: > Sorry, i missed to attach the project > > Eduardo Alonso > Vía de las dos Castillas, 33, Ática 4, 3ª Planta > 28224 Pozuelo de Alarcón, Madrid >

<    1   2   3   4   5   >