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: twitter.png] https

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 [image: twitter.png] https

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: Is it possible to group by timestamp in hour, day, weeks.. in Cassandra?

r goup 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: > >

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:

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 >

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 >

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

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:

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" <benjamin.le...@datastax.com> wrote: > > >Hi Chris, > > > &

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

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--- > pk | rc &

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

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

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 >

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:

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 >

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 >

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

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

Re: Typo in comment for maxFunctionForCounter in AggregateFcts.java

Done. Thanks for reporting the problem. On Tuesday, April 19, 2016, Benjamin Lerer <benjamin.le...@datastax.com> 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 <jack.krupan...@gm

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. > */ >

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.

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

Re: Performance issue in 3.0.9

Guys, If you really want us to improve the things you need to be a bit more helpfull. We have no clue of what are the problems or changes in preformance that you see. So, if you could provide more context and facts it would be great. The more help and clarity you can provide, the easier it will

Re: Why does CockroachDB github website say Cassandra has no Availability on datacenter failure?

May be you should ask them? We are not involved in the CockroachDB github website. On Tue, Feb 7, 2017 at 11:41 AM, Kant Kodali wrote: > Why does CockroachDB github website say Cassandra has no Availability on > datacenter failure? > > https://github.com/cockroachdb/cockroach

Re: Why does CockroachDB github website say Cassandra has no Availability on datacenter failure?

Do not get angry for that. It does not worth it. :-) On Tue, Feb 7, 2017 at 1:11 PM, Kant Kodali wrote: > lol. But seriously are they even allowed to say something that is not true > about another product ? > > On Tue, Feb 7, 2017 at 4:05 AM, kurt greaves

Re: Why does CockroachDB github website say Cassandra has no Availability on datacenter failure?

If you do not like it, feel free to leave the mailing list :-) On Tue, Feb 7, 2017 at 1:45 PM, Bernardo Sanchez < bernard...@pointclickcare.com> wrote: > guys this isn't twitter. stop your stupid posts > > From: benjamin.le...@datastax.com > Sent: February 7, 2017 7:43 AM > To:

Re: Why does CockroachDB github website say Cassandra has no Availability on datacenter failure?

... and by the way, it is far from being the only wrong stuff in their list. On Tue, Feb 7, 2017 at 11:57 AM, Benjamin Lerer <benjamin.le...@datastax.com > wrote: > May be you should ask them? We are not involved in the CockroachDB github > website. > > On Tue, Feb 7, 2017

Re: unexpected select result on secondary index on static column

Micha, I did not had the time to look into your problem yet. Could you open a JIRA ticket to be sure that we do not forget about this problem? I will look into it as soon as I can. On Mon, Jan 30, 2017 at 5:12 PM, Benjamin Lerer <benjamin.le...@datastax.com > wrote: > I do not se

Re: unexpected select result on secondary index on static column

I will try to reproduce the problem. Thanks for the information On Mon, Jan 30, 2017 at 2:34 PM, Micha wrote: > I have restarted the three node cluster with new directories for data > and commitlog and made the test again. > > This time the resultset size is 62 rows for

Re: unexpected select result on secondary index on static column

Hi Michael, It sound like a bug but I could not reproduced it on 3.9 or on the current 3.11 branch (which will become 3.10). Now, that does not mean that there are not problem. Something might be different in your environement. Do you still see that problem when you start from a clean environment

Re: unexpected select result on secondary index on static column

he three-node cluster with a keyspace with replication > factor of 1 and see what happens. > I left most of the default config of cassandra untouched, except storage > directories and ip addresses. > > Cheers, > Michael > > > > > > > > On 30.01.2017 10:

Re: unexpected select result on secondary index on static column

se CQLSH to reproduce the problem or another client? On Mon, Jan 30, 2017 at 2:39 PM, Benjamin Lerer <benjamin.le...@datastax.com > wrote: > I will try to reproduce the problem. > Thanks for the information > > On Mon, Jan 30, 2017 at 2:34 PM, Micha <mich...@fantasymail.de>

Re: unexpected select result on secondary index on static column

ication factor 2 (or 1) -> wrong result. > > > Are there restrictions on the replication factor? Does this matter as > the index is stored locally (as I have read)? > > I did use cqlsh and also get the same result when using the java api. > > Thanks for helping, > Michael > >

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

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

Re: cassandra unit test

Unit tests run only a single server instance. I you want to use multiple servers in your test you should write a DTest ( https://github.com/riptano/cassandra-dtest). Hope it helps. Benjamin On Tue, Sep 6, 2016 at 4:59 AM, Stone Fang wrote: > Call QueryProcessor.execute

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

Re: restrictions on IN operator

ere is the version details of cassandra: > > show version; > [cqlsh 5.0.1 | Cassandra 3.7 | CQL spec 3.4.2 | Native protocol v4] > > when IN conditions can be run on any (clustering) column, then i suppose > non-equal conditions should also be supported. is my expectation wrong?

Re: Failing tests 2016-09-14

SelectTest start to be pretty big. It makes sense to splitting it into separate TestClasses. For example we could extract all the filtering tests into a new TestClass: FilteringTest or SelectWithFilteringTest. On Thu, Sep 15, 2016 at 8:34 AM, Oleksandr Petrov < oleksandr.pet...@gmail.com> wrote:

Re: Question on assert

We can spend hours arguing about assert vs exceptions. I have seen it happen in every company I worked for. Overall, based on the patches I have reviewed, it seems to me that in general people are using them only has internal safety checks. Unfortunatly, the code change and we can miss things. If

Re: Question on assert

should all be moved over to junit asserts. > > > > On 09/22/2016 03:52 AM, Benjamin Lerer wrote: > >> We can spend hours arguing about assert vs exceptions. I have seen it >> happen in every company I worked for. >> Overall, based on the patches I have reviewed, it see

Re: Low hanging fruit crew

Having the test passing does not mean that a patch is fine. Which is why we have a review check list. I never put a patch available without having the tests passing but most of my patches never pass on the first try. We always make mistakes no matter how hard we try. The reviewer job is to catch

Re: Cassandra Mutation object decoding

> > My goal is to reconstruct the CQL operation from the Mutation object. > So that I can trigger the same action on another NoSQL target like MongoDB. > There are different way of keeping your 2 database in sync. Unfortunatly, they all have some trade offs (as always ;-)) 1. If you have

Re: Cassandra Mutation object decoding

Hi Sanal, What you want to do is not an easy stuff and it might break with new major releases. My question would be: why do you want to do that? There might be another way to reach the same goal. Benjamin On Mon, Nov 21, 2016 at 7:14 PM, Sanal Vasudevan wrote: > Thank

cassandra-3.11 and the new merge order

Hi, I created a new cassandra-3.11 branch. By consequence, the new merge order for bug fixe is: 2.2 -> 3.0.X -> 3.11 -> 3.X -> trunk and the new merge order for improvements is: 3.X -> trunk 3.X will then be released as 3.12 and trunk as 4.0. Benjamin

Re: Bug in paging reads and limit reads (short reads!)

A, so I don't know conventions to set priority. As its > data inconsistency issue, I believe this is critical. Feel free to change > the priority according to community conventions. > > Thanks, > Bhaskar > > On Wed, Nov 2, 2016 at 1:26 AM, Benjamin Lerer < > benjamin.le...@d

Re: Bug in paging reads and limit reads (short reads!)

Hi Bhaskar, Thanks for reporting that problem. It is a nice catch :-) Could you open a JIRA ticket with all the information that you provided? I will try to fix that problem. Benjamin On Wed, Nov 2, 2016 at 12:00 AM, Bhaskar Muppana wrote: > Hi Guys, > > We are seeing

Re: CASSANDRA-8596

Hi Vladimir, It also seems that the ticket has never been marked as patch available and that you did not assign yourself to it. Most of us look at those to determine in which state is a ticket. On Tue, Nov 29, 2016 at 9:42 AM, Jeff Jirsa wrote: > Hey Vladimir > > Always nice

Re: CASSANDRA-8596

One of the problem is that we have to deal with a huge number of tickets. We could let them open forever or close the ones that we think are not real problems or that we know we will never have time to do. CASSANDRA-8954 has been opened for a year before Aleksey closed it. When those things happen

Re: Per blockng release on dtest

Regarding CASSANDRA-12620, it has been committed in the 3.0 branch at c612cd8d7dbd24888c216ad53f974686b88dd601 and merged into 3.11. As, if I am not mistaken, 3.11 should become the new 3.10 release, I do not think that there is a problem. Did I miss something Ariel? On Tue, Jan 10, 2017 at 6:45

Re: API for Cassandra CQL

Sorry, This feature does not exist. On Wed, Mar 29, 2017 at 3:13 AM, Ramesh Mani wrote: > Hello Cassandra team members, > > I am looking for API via which I can get the CQL session query as string? > Is there a way I can get the Query executed by the users via API > >

Re: Move 3.11.x unresolved features and improvements to 4.0

Sorry, I misunderstood the email. Aleksey, took care of the commited patches. I agree all the open 3.11.x features and improvements should be moved to 4.0. On Fri, Apr 28, 2017 at 5:04 PM, Benjamin Lerer <benjamin.le...@datastax.com > wrote: > I think that Aleksey already

SSTablesPerReadHistogram, Tracing and SSTableReader::readCount values seems incorrect

Hi, While working on CASSANDRA-13120, I came to realize that since 3.0 we are using for SSTablesPerReadHistogram, Tracing and SSTableReader::readCount the number of SSTables for which we did a partition lookup and not the number of SSTables

Re: Commitlog without header

It might be related to CASSANDRA-12539 (in cassandra-2.2.9). We used to use 2 file pointers when creating commitlog segments. So if you run out of file pointers while requesting the second file pointer you would end up with an empty segment.

Which approach should we use for exposing metrics through Virtual tables?

Hi, I would like to start working on exposing the metrics through virtual tables in CASSANDRA-14537 We had some long discussion already in CASSANDRA-7622 about which schema to use to expose the metrics, unfortunately in the end I was not

Re: Would cqlsh describe command send query to cassandra server ?

Hi, DESCRIBE commands are handled at the driver level not at the server level. The drivers fetch metadata and keep them up to date. When a DESCRIBE command is send, the driver build the output from those metadata. Benjamin On Tue, Aug 7, 2018 at 1:33 PM, 陈仕（shichen）-技术产品中心 wrote: > > Hello,

Re: NEQ-restriction in select-where clause

It can be done for filtering, otherwise it is really tricky (I am not even sure it can be done to be honest). On Sun, Sep 9, 2018 at 2:11 AM, Dmitry Lazurkin wrote: > Hello. > > Does it make sense to implement != restriction in select-where clause? > Is it possible? > > Thank you. > > PS. I

Re: Optimizing queries for partition keys

ther it's also potentially worth contributing. > > Thanks, > Sk > > > On 2018-03-22 18:16, Benjamin Lerer wrote: > >> You should check the 3.x release. CASSANDRA-10657 could have fixed your >> problem. >> >> >> On Thu, Mar 22, 2018 at 9:15 PM, Benja

Re: Optimizing queries for partition keys

Syvlain explained the problem in CASSANDRA-4536: " Let me note that in CQL3 a row that have no live column don't exist, so we can't really implement this with a range slice having an empty columns list. Instead we should do a range slice with a full-row slice predicate with a count of 1, to make

Re: Paying off tech debt and correctly naming things

I agree that the refactoring make sense but I also know the pain of merging branches with smaller refactorings. When you have to make a patch for several branches and that you have to go through several round of reviews it can be pretty painful. I know that pain too well so I am not in favor of

Re: Optimizing queries for partition keys

You should check the 3.x release. CASSANDRA-10657 could have fixed your problem. On Thu, Mar 22, 2018 at 9:15 PM, Benjamin Lerer <benjamin.le...@datastax.com > wrote: > Syvlain explained the problem in CASSANDRA-4536: > " Let me note that in CQL3 a row that have no live colum

Re: IN restrictions are not supported on indexed columns

There are not real blocker I believe. It is just that we never implemented it. On Fri, Mar 23, 2018 at 6:08 PM, Dikang Gu wrote: > Hello C* developers: > > I have one question, does anyone know why we can not support the IN > restrictions on indexed columns? Is it just

Re: Implicit Casts for Arithmetic Operators

Hi, I would like to try to clarify things a bit to help people to understand the true complexity of the problem. The *float *and *double *types are inexact numeric types. Not only at the operation level. If you insert 676543.21 in a *float* column and then read it, you will realize that the

Re: Implicit Casts for Arithmetic Operators

> >>>>>>>>>>> " > >>>>>>>>>>> > >>>>>>>>>>> And this makes sense to me. I think we should only return an > >> exact > >>>>>>>> result if both of the i

Re: Implicit Casts for Arithmetic Operators

Sorry, following a standard for the sake of following a standard does not make sense to me. On Thu, Nov 22, 2018 at 12:33 PM Benedict Elliott Smith wrote: > Yes. > > > On 22 Nov 2018, at 11:32, Benjamin Lerer > wrote: > > > > Then I would be interested

Re: Implicit Casts for Arithmetic Operators

gt; >>>>>>> condition > >>>>>>>>>>>>> is raised. If least significant digits are lost, > >>>>>>> implementation- > >>>>>>>>>>>>> defined rounding or t

Re: Stability of MaterializedView in 3.11.x | 4.0

Hi Pankaj, The main issues are described in the link you posted and are some synchronization issues * There's no way to determine if a view is out of sync with the base table. * If you do determine that a view is out of sync, the only way to fix it is to drop and rebuild the view. Even in the

Re: [proposal] Introduce AssertJ in test framework

+1 On Tue, Mar 10, 2020 at 6:18 PM Jon Haddad wrote: > I've used assertj in a lot of projects, I prefer it by a wide margin over > using only junit. > > On Tue, Mar 10, 2020 at 9:45 AM David Capwell wrote: > > > +1 from me > > > > In CASSANDRA-15564 I build my own assert chain to make the

Re: Keeping test-only changes out of CHANGES.txt

+1 On Thu, Apr 9, 2020 at 9:28 AM Eduard Tudenhoefner < eduard.tudenhoef...@datastax.com> wrote: > updated docs in https://github.com/apache/cassandra/pull/528 > > On Wed, Apr 8, 2020 at 11:39 PM Jordan West wrote: > > > +1 (nb) to the change and +1 (nb) to updating the docs to reflect this.

Re: [VOTE] Release Apache Cassandra 4.0-alpha4

+1 On Tue, Apr 14, 2020 at 5:50 PM Blake Eggleston wrote: > +1 > > > On Apr 14, 2020, at 5:09 AM, e.dimitr...@gmail.com wrote: > > > > I also can’t see them. I think it matters to which interface is the > link. > > > > And +1 from me, thanks! > > > >> On 14 Apr 2020, at 7:53, Erick Ramirez >

Re: server side describe

changes that weren't discussed yet - we can talk over. If it's > something as > trivial as server-side describe that doesn't risk stability but adds a > lot > of value, it may make sense to include. But I woudln't attempt to come > up > with a general rule for what we may or

Re: server side describe

> > tables > > > >> because its what the initial feedback was to do. Robert added a lot > of > > > >> functionality on top of what was there which is what people were > > > starting > > > >> to ask for. I am in favor of just goi

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

Re: server side describe

It seems to me that we need to get better at making decisions for things like that. If we keep on arguing for small things, it will simply be time consuming and painfull for everybody. In this case, the situation seems simple. Part of the group do not agree with the proposal. We just have to

Re: server side describe

+1 for shipping it after 4.0 On Thu, Apr 2, 2020 at 12:39 AM Jon Haddad wrote: > Most of the work to provide this feature is already done. We need to > generate server side CQL for snapshots already. All we need to do is > expose it via either a "DESCRIBE" CQL command, or I'm equally happy

Re: server side describe

We have already discussed it for several days and I believe that all the points have been brought to the table. I took the time to read CASSANDRA-14825 this morning to understand the full story. All the discussion has been about using Virtual Tables versus using DESCRIBE. My understanding is that

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)

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: [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: > > >

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: > >

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: > > >

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: > > >

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: 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

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

Re: [DISCUSS] Stabilizing 4.0

ken=A5KQ-2QAV-T4JA-FDED_fd75a3db98350d94229fbb4cf29cb50f3051d7ce_lin=Next On Tue, Jun 30, 2020 at 10:20 AM Benjamin Lerer wrote: > 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

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

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

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

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

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

Re: [DISCUSS] When to branch 4.0

external 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:10, "

Re: [DISCUSS] When to branch 4.0

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 thread. > > I recommend we let this thread di

  1   2   3   4   >