intent of working on
> > > compaction from a purely architectural standpoint. I think this type
> of
> > > thing should be done throughout the codebase.
> > >
> > > Removing the singletons is a good first step, my vote is we just rip
> off
> >
On Mon, Mar 27, 2017 at 7:03 PM, Josh McKenzie wrote:
> How do we plan on verifying #4? Also, root-cause to tie back new code that
> introduces flaky tests (i.e. passes on commit, fails 5% of the time
> thereafter) is a non-trivial pursuit (thinking #2 here), and a pretty
> common problem in this
On Thu, Mar 23, 2017 at 12:42 PM, Daryl Hawken
wrote:
> +1.
>
> On Thu, Mar 23, 2017 at 12:10 PM, Michael Shuler
> wrote:
>
> > I won't reply to the obvious spam to hilight it any further, so new
> > message..
> >
> > Could the mailing list moderator that approved the "client list" message
> > i
Well that is quite unsettling.
On Thu, Mar 23, 2017 at 10:33 AM, Theresa Taylor <
theresa.tay...@onlinedatatech.biz> wrote:
> Hi,
>
> Would you be interested in acquiring a list of DataStax users' information
> in an Excel sheet for unlimited marketing usage?
>
> List includes – First and Last na
On Thu, Mar 23, 2017 at 10:56 AM, Eric Evans
wrote:
> On Wed, Mar 22, 2017 at 10:01 AM, Edward Capriolo
> wrote:
> > I believe you could accomplish a similar goal by making a multi-module
> > project https://maven.apache.org/guides/mini/guide-multiple-modules.html
> .
>
On Tue, Mar 21, 2017 at 5:45 PM, Anthony Grasso
wrote:
> This is a great idea
>
> +1 (non-binding)
>
> On 22 March 2017 at 07:04, Edward Capriolo wrote:
>
> > On Tue, Mar 21, 2017 at 3:24 PM, Mark Dewey wrote:
> >
> > > I can immediately thi
On Tue, Mar 21, 2017 at 3:24 PM, Mark Dewey wrote:
> I can immediately think of a project I would use that in. +1
>
> On Tue, Mar 21, 2017 at 12:18 PM Jonathan Haddad
> wrote:
>
> > I created CASSANDRA-13284 a few days ago with the intent of starting a
> > discussion around the topic of breaking
Wikis are still good for collaberative design etc. Its a burden to edit the
docs and its not the place for all info.
On Friday, March 17, 2017, Murukesh Mohanan
wrote:
> I wonder if the recent influx has anything to do with GSoC. The student
> application period begins in a few days. I don't see
the intent of working on
> > > compaction from a purely architectural standpoint. I think this type
> of
> > > thing should be done throughout the codebase.
> > >
> > > Removing the singletons is a good first step, my vote is we just rip
> off
> >
gt; making that system easier to work with/test) seems like an achievable
> goal.
> >
> > On Fri, Mar 17, 2017 at 10:17 AM, Edward Capriolo >
> > wrote:
> >
> >> On Fri, Mar 17, 2017 at 12:33 PM, Blake Eggleston >
> >> wrote:
> >>
> &g
On Fri, Mar 17, 2017 at 12:33 PM, Blake Eggleston
wrote:
> I think we’re getting a little ahead of ourselves talking about DI
> frameworks. Before that even becomes something worth talking about, we’d
> need to have made serious progress on un-spaghettifying Cassandra in the
> first place. It’s a
On Fri, Mar 17, 2017 at 9:46 AM, Edward Capriolo
wrote:
>
>
> On Fri, Mar 17, 2017 at 6:41 AM, Ryan Svihla wrote:
>
>> Different DI frameworks have different initialization costs, even inside
>> of
>> spring even depending on how you wire up dependencies (did it u
ooking at it's feature set,
> that's my guess) , Spring I know from experience even with the most optimal
> settings is slower on initialization time than doing by DI "by hand" at
> minimum, and that can sometimes be substantial.
>
>
> On Mar 17, 2017 12:29 AM
>
> On Thu, Mar 16, 2017 at 2:04 PM, Qingcun Zhou
> wrote:
>
> > Since we're here, do we have plan to integrate with a dependency
> injection
> > framework like Dagger2? Otherwise it'll be difficult to write unit test
> > cases.
> >
> > On Thu, M
On Thu, Mar 16, 2017 at 3:10 PM, Jeff Jirsa wrote:
>
>
> On 2017-03-16 10:32 (-0700), François Deliège
> wrote:
> >
> > To get this started, here is an initial proposal:
> >
> > Principles:
> >
> > 1. Tests always pass. This is the starting point. If we don't care
> about test failures, then we
On Sat, Mar 4, 2017 at 10:26 AM, Jeff Jirsa wrote:
>
>
>
> > On Mar 4, 2017, at 7:06 AM, Edward Capriolo
> wrote:
> >
> >> On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa wrote:
> >>
> >> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo
>
On Saturday, March 4, 2017, Edward Capriolo wrote:
>
>
> On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa > wrote:
>
>> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo > >
>> wrote:
>>
>> >
>> > I used them. I built do it yourself secondary i
On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa wrote:
> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo
> wrote:
>
> >
> > I used them. I built do it yourself secondary indexes with them. They
> have
> > there gotchas, but so do all the secondary index implementati
On Thu, Mar 2, 2017 at 2:10 PM, Kant Kodali wrote:
> +1
>
> On Thu, Mar 2, 2017 at 11:04 AM, S G wrote:
>
> > Hi,
> >
> > I am not able to find any documentation on the current state of triggers
> > being production ready.
> >
> > The post at
> > http://www.datastax.com/dev/blog/whats-new-in-cas
Older versions had a request scheduler api.
On Monday, February 20, 2017, Ben Slater > wrote:
> We’ve actually had several customers where we’ve done the opposite - split
> large clusters apart to separate uses cases. We found that this allowed us
> to better align hardware with use case requirem
Three cheers!
Hip , Hip, NotFound
1 ms later
Hip, Hip, Hooray
1 ms later
Hooray, Hooray, Hooray
On Tue, Feb 14, 2017 at 5:50 PM, Ben Bromhead wrote:
> Congrats!!
>
> On Tue, 14 Feb 2017 at 13:37 Joaquin Casares
> wrote:
>
> > Congratulations!
> >
> > +1 John's sentiments. That's a great list of
On Sat, Feb 11, 2017 at 3:03 AM, Benjamin Roth
wrote:
> For MVs regarding this threads question only the partition key matters.
> Different primary keys can have the same partition key. Which is the case
> in the example in your last comment.
>
> Am 10.02.2017 20:26 schrieb "Kant Kodali" :
>
> @B
If you want to test the scenarios thia project would be helpful
Http://github.com/edwardcapriolo/ec
I use brute force at different CL and assert if i detect and consistency
issues. Having mvs would be nice
On Saturday, February 11, 2017, Benjamin Roth
wrote:
> For MVs regarding this threads qu
On Tue, Feb 7, 2017 at 8:12 AM, Kant Kodali wrote:
> yes agreed with this response
>
> On Tue, Feb 7, 2017 at 5:07 AM, James Carman
> wrote:
>
> > I think folks might agree that it's not worth the time to worry about
> what
> > they say. The ASF isn't a commercial entity, so we don't worry abou
On Fri, Feb 3, 2017 at 6:52 PM, Michael Shuler
wrote:
> The Cassandra team is pleased to announce the release of Apache
> Cassandra version 3.10.
>
> Apache Cassandra is a fully distributed database. It is the right choice
> when you need scalability and high availability without compromising
> p
On Tuesday, January 10, 2017, Romain Hardouin
wrote:
> To be able to downgrade we should be able to pin both commitlog and
> sstables versions, e.g. -Dcassandra.commitlog_version=3
> -Dcassandra.sstable_version=jb
> That would be awesome because it would decorrelate binaries version and
> data ve
I will take this up at the next NYC-cassandra meetup. I have been on the
fence for "charging" for events for a while, but a nice donation piece
would be pretty cool if it can fuel the project.
I have also joked about creating CaSETI (Search for Extra Testing
Infrastructure) and building a docker t
I think it is fair to run a flakey test again. If it is determine it flaked
out due to a conflict with another test or something ephemeral in a long
process it is not worth blocking a release.
Just deleting it is probably not a good path.
I actually enjoy writing fixing, tweeking, tests so pinge
mber 19, 2016, Jeff Jirsa wrote:
> Any proposal to solve the problem you describe?
>
> --
> Jeff Jirsa
>
>
> > On Nov 19, 2016, at 8:50 AM, Edward Capriolo > wrote:
> >
> > This is especially relevant if people wish to focus on removing things.
> >
> >
t; Honest question: are you *ever* positive Ed?
>
> Maybe give it a shot once in a while. It will be good for your mental
> health.
>
>
> Sent from my iPhone
>
> > On Nov 19, 2016, at 11:50 AM, Edward Capriolo > wrote:
> >
> > This is especially relevant if p
probably switch but its not stable
and we have that one compact storage cf and who knows what is going to
happen performance wise when)
We really need to lose this realease wont be stable for 6 minor versions
concept.
On Saturday, November 19, 2016, Edward Capriolo
wrote:
>
>
> On Friday,
On Friday, November 18, 2016, Jeff Jirsa wrote:
> We should assume that we’re ditching tick/tock. I’ll post a thread on
> 4.0-and-beyond here in a few minutes.
>
> The advantage of a prod release every 6 months is fewer incentive to push
> unfinished work into a release.
> The disadvantage of a p
These tickets claim to duplicate each other:
https://issues.apache.org/jira/browse/CASSANDRA-12674
https://issues.apache.org/jira/browse/CASSANDRA-12746
But one is marked fixed and the other is still open.
What is the status here?
On Thu, Nov 17, 2016 at 5:20 PM, DuyHai Doan wrote:
> Be very
. scylladb).
> >
> > And since there was quote battle on twitter between Jim Jagielski and
> > Benedict, I can throw some in as well. Over conferences I attended and
> even
> > during consultancy services I got, I’ve spoken with some people having
> > records of
storically very poor
> indeed, but is I believe much stronger today - try not to judge current
> behaviours on those of the past)
>
>
> On 5 November 2016 at 00:05, Edward Capriolo
> wrote:
>
> > "I’m sure users running Cassandra in production would prefer actual
&
h a thing happening.
>
> I’m sure users running Cassandra in production would prefer actual proper
> reviews to non-review +1s.
>
> --
> AY
>
> On 4 November 2016 at 23:03:23, Edward Capriolo (edlinuxg...@gmail.com)
> wrote:
>
> I feel that is really standing up on a soap box. What would be the worst
> thing that happens here
"There is also the issue of specialisation. Very few people can be trusted
with review of arbitrary
Cassandra patches. I can count them all on fingers of one hand."
I have to strongly disagree here. The Cassandra issue tracker is over
12000 tickets. I do not think that cassandra has added 12000 "
On Thu, Nov 3, 2016 at 11:44 PM, Kelly Sommers
wrote:
> I think the community needs some clarification about what's going on.
> There's a really concerning shift going on and the story about why is
> really blurry. I've heard all kinds of wild claims about what's going on.
>
> I've heard people s
Is the message in moderation because
1) it was sent by someone not registered with the list
2) some other reason (anti-spam etc)
If it is is case 1: Isn't the correct process to inform and encourage
someone list properly?
If it is case 2: Is there an expected ETA for list moderation events?
(proba
I would like to propose features around seeds:
https://issues.apache.org/jira/browse/CASSANDRA-12627
I have other follow up issues like getting seeds from Amazon API, or from
JNDI/ DNS, etc.
I was hoping 12627 was an easy way to grease the wheels.
On Fri, Nov 4, 2016 at 8:39 AM, Jason Brown wr
Also no one has said anything to the effect of 'we want to rubber stamp
reviews' so that ...evil reason. Many of us are coders by trade and
understand why that is bad.
On Wednesday, October 19, 2016, Edward Capriolo
wrote:
> I realize that test passing a small tests and trivial rev
I realize that test passing a small tests and trivial reviews will not
catch all issues. I am not attempting to trivialize the review process.
Both deep and shallow bugs exist. The deep bugs, I am not convinced that
even an expert looking at the contribution for N days can account for a
majority
Yes. The LHFC crew should always pay it forward. Not many of us have a
super computer to run all the tests, but for things that are out there
marked patch_available apply it to see that it applies clean, if it
includes a test run that test (and possibly some related ones in the
file/folder etc for
I want to point out something:
https://issues.apache.org/jira/browse/CASSANDRA-6846
"I'm definitively -1 on putting any type of contract on the internals. They
are called internals for a reason, and if rewriting it all entirely
tomorrow is best for Cassandra, we should have the possibility to do
IMHO, while through the code. A vast majority of the //comments would be
better as /** */ comments in method declarations. Many believe that
excessive inline comments could indicate a code smell.
On Tue, Oct 18, 2016 at 1:21 PM, Josh McKenzie wrote:
> >
> > tests hastily and messly commented o
I go through the Cassandra jira weekly and I notice a number of tickets
which appear to be clear issues or requests for simple metrics.
https://issues.apache.org/jira/browse/CASSANDRA-12626
https://issues.apache.org/jira/browse/CASSANDRA-12330
I also have a few jira issues (opinion) would be sim
I have contemplated using LocalStrategy as a "do it yourself client side
sharding system".
On Sat, Oct 8, 2016 at 12:37 AM, Vladimir Yudovin
wrote:
> Hi Prasenjit,
> I would like to get the replication factors of the key-spaces using the
> strategies in the same way we get the replication factor
I have a similar set of problems. I will set the stage: in the past, for a
variety of reasons I had to create tables(column families) by time range
for an event processing system.
The man reason was expiring data (TTL) did not purge easily. It was easier
to simply truncate/drop old column families
I love DTest I think it is a great thing in the tool belt. One thing that I
want to point out, nosettests and dtests are black-box type testing. You
can not step or trace these things very easily.
My dream would be if cassandra was re-entrant and it was possible to run a
3 node cluster in one JVM
Yes obviously we do not need to go in and replace them all at once. Some
rough guidance/general consensus should be in place, because we are
violating the standard usage:
https://docs.oracle.com/javase/8/docs/technotes/guides/language/assert.html
Do *not* use assertions for argument checking in p
ng n00b users to get
> a mythical 5% performance increase and then get silent corruption when
> their disk/io goes sideways and the asserts might have caught things before
> it went really wrong.
>
> Sent from my iPhone
>
> On Sep 21, 2016, at 10:31 AM, Edward Capriolo <mai
out a potential 5% performance win
> when you've corrupted all their data.
>
> best,
> kjellman
>
> > On Sep 21, 2016, at 10:21 AM, Edward Capriolo
> wrote:
> >
> > There are a variety of assert usages in the Cassandra. You can find
> several
> &
There are a variety of assert usages in the Cassandra. You can find several
tickets like mine.
https://issues.apache.org/jira/browse/CASSANDRA-12643
https://issues.apache.org/jira/browse/CASSANDRA-11537
Just to prove that I am not the only one who runs into these:
https://issues.apache.org/jira
If you all have never seen the movie "grandma's boy" I suggest it.
https://www.youtube.com/watch?v=uJLQ5DHmw-U
There is one funny seen where the product/project person says something
like, "The game is ready. We have fixed ALL THE BUGS". The people who made
the movie probably think the coders doi
"The historical trend with the Cassandra codebase has been to test
minimally,
throw the code over the wall, and get feedback from people putting it in
prod who run into issues."
At the summit Brandon and a couple others were making fun over range
tombstones from thrift
https://issues.apache.org/ji
It is funny you say this:
"tick-tock started based off of the 3.0 big bang “we broke everything”
release"
*"Brain battles itself over short-term rewards, long-term goals"*
https://www.princeton.edu/pr/news/04/q4/1014-brain.htm
*Normalization of deviance in software: how broken practices become
s
Where did we come from?
We came from a place where we would say, "You probably do not want to run
2.0.X until it reaches 2.0.6"
One thing about Cassandra is we get into a situation where we can only go
forward. For example, when you update from version X to version Y, version
Y might start writin
>> I think it goes the other way around. When you push to ASF git with the
right commit message then the integration from that side closes the pull
request.
Yes. This is how apache-gossip is setup. Someone makes a JIRA and they
include a link to there branch and tell me they are done. We review
g
Yes. I did. My bad.
On Fri, Aug 26, 2016 at 4:07 PM, Jason Brown wrote:
> Ed, did you mean this to post this to the other active thread today, the
> one about github pull requests? (just want to make sure I'm understanding
> correctly :) )
>
> On Fri, Aug 26, 2016 at 12:28
One thing to watch out for. The way apache-gossip is setup the PR's get
sent to the dev list. However the address is not part of the list so the
project owners get an email asking to approve/reject every PR and comment
on the PR.
This is ok because we have a small quite group but you probably do n
What a fun topic. I re-joined the list just for this.
As I understand, it the nature of the Apache Software Licence any corporate
entity is allows to produce open and closed source software based on Apache
Cassandra, however the Cassandra name is a trademark of the ASF foundation.
As I under it,
do into fighting for
> Thrift, I'm scared to think how amazing CQL would be.
>
> Best,
> Michael
>
> > On Mar 13, 2014, at 5:59 AM, "Edward Capriolo"
> wrote:
> >
> > There was a paging bug in 2.0 and a user just reported a bug sorting a
>
There was a paging bug in 2.0 and a user just reported a bug sorting a one
row dataset.
So if you want to argue cql has surpassed thrift in all ways, one way it
clearly has not is correctness.
To demonatrate, search the changelog for cql bugs that return wrong result.
Then do the same search for
to add features, call a vote
and add language to stop them.
+1
On Wednesday, March 12, 2014, Sylvain Lebresne wrote:
> On Wed, Mar 12, 2014 at 1:38 PM, Edward Capriolo wrote:
>
>> ", I don't know of any use cases for Thrift that can't be
>> > done in CQL"
", I don't know of any use cases for Thrift that can't be
> done in CQL"
Can dynamic composites be used from CQL?
On Wed, Mar 12, 2014 at 4:44 AM, Sylvain Lebresne wrote:
> +1 to Jonathan's proposal.
>
>
> On Tue, Mar 11, 2014 at 6:00 PM, Jonathan Ellis wrote:
>
> > CQL3 is almost two years ol
face.
>
> I still seem to remember there was a few angry users when Avro was removed.
>
>
> On Tue, Mar 11, 2014 at 8:04 PM, Edward Capriolo >wrote:
>
> > With support officially deprecated that will be the only way to go. If a
> > user wants to add a function to thrif
order.
On Tue, Mar 11, 2014 at 7:46 PM, Russ Bradberry wrote:
> I would like to suggest the possibility of having the interface somewhat
> pluggable so another project can provide the Thrift interface as a drop in
> JAR. Thoughts?
>
> Sent from my iPhone
>
> > On Mar 11,
removal of
> > Thrift in the trunk, but I think there is a use-case for an extensible
> > interface.
> >
> > I still seem to remember there was a few angry users when Avro was
> removed.
> >
> >
> > On Tue, Mar 11, 2014 at 8:04 PM, Edward Capriolo >
If you are using thrift there probably isn't a reason to upgrade to 2.1
What? Upgrading gets you performance regardless of your api.
We have already gone from "no new feature" talk to "less enphisis on
testing".
How comforting.
On Tuesday, March 11, 2014, Dave Brosius wrote:
>
> +1,
>
> altho s
11, 2014 at 3:38 PM, Edward Capriolo
> wrote:
> > "I am confused how any of this is relevant to Jonathan's original email."
> >
> > Here is how:
> >
> > I believe if native is the new official transport, Cassandra should
> include
> >
op the
software.
On Tue, Mar 11, 2014 at 4:24 PM, Brandon Williams wrote:
> I am confused how any of this is relevant to Jonathan's original email.
>
>
> On Tue, Mar 11, 2014 at 3:13 PM, Edward Capriolo >wrote:
>
> > "How about the myriad of thrift wrappers that
t 3:13 PM, Edward Capriolo
> wrote:
> > "How about the myriad of thrift wrappers that aren't in-tree either?"
> >
> > How about all the times we trashed hbase saying "hbase treats non java
> > people like second class citizens"
> >
&g
-+u4ssdmdsmp2dgrst90hoypw...@mail.gmail.com%3E
Nice to see us pulling a total 180.
On Tue, Mar 11, 2014 at 4:09 PM, Brandon Williams wrote:
> How about the myriad of thrift wrappers that aren't in-tree either?
>
>
> On Tue, Mar 11, 2014 at 3:03 PM, Edward Capriolo >wrote:
>
&
Mar 11, 2014 at 2:24 PM, Edward Capriolo >wrote:
>
> > "The native protocol spec is the source of truth. If Cassandra's
> behavior
> > doesn't match the spec, it's a bug. Likewise for any drivers. I'm not
> > sure how this makes it unclear
rites the driver?
mysql. Where is the source code for this driver? Inside the same repository
as the server. Cassandra should be the same way.
On Tue, Mar 11, 2014 at 2:58 PM, Tyler Hobbs wrote:
> On Tue, Mar 11, 2014 at 1:37 PM, Edward Capriolo >wrote:
>
> >
> > 1) Who doe
I am -1. For a few reasons:
Cassandra will be the only database ( that I know of ) where the only
official client to the database will live in source control outside of the
project. I would like some clarity on this development will go on in an
open source fashion. Namely:
1) Who does and how do
Check intravert on github. I am working t get many of those features into
cassandra.
On Thursday, February 27, 2014, Brandon Williams wrote:
> A few:
>
> https://issues.apache.org/jira/browse/CASSANDRA-4914
>
> https://issues.apache.org/jira/browse/CASSANDRA-5184
>
> https://issues.apache.org/jir
This is always so hard to explain but
http://www.datastax.com/dev/blog/thrift-to-cql3
Get to the part that looks like this:
update column family user_profiles
with key_validation_class = UTF8Type
and comparator = UTF8Type
and column_metadata=[]
"Since the static column values validation types h
If you understand how cql collections are written you can decode them and
work with them from thrift. It's quite a chore and i would not suggest
trying yo do it however.
(I suspect tyler tried it and jonathan broke his hand jk)
There is a perl cassandra driver that did something like this.
On We
This makes sense. Unless you are running major compaction a delete could
only happen if the bloom filters confirmed the row was not in the sstables
not being compacted. If your rows are wide the odds are that they are in
most/all sstables and then finally removing them would be tricky.
On Thu, Ma
I am not sure about the collection case. But for compact storage you can
specify multiple-ranges in a slice query.
https://issues.apache.org/jira/browse/CASSANDRA-3885
I am not sure this will get you all the way to bit-map indexes but in a
wide row scenario it seems like you could support a "even
t; schema's can give someone the rope to hang themselves.
> *
> For those of us that know what we are doing and have had to put up with SQL
> based ETL, refining CQL3 would be life changing and ease the transition.
>
> ap
>
>
>
>
> On Wed, Mar 6, 2013 at 8:08 A
QL tables to be very different and essentially
not compatible with each other.
With schema and cassandra less is more.
On Tue, Mar 5, 2013 at 4:08 PM, Edward Capriolo wrote:
>
> http://www.edwardcapriolo.com/roller/edwardcapriolo/entry/schema_vs_schema_less
>
> Does your the tool handle t
http://www.edwardcapriolo.com/roller/edwardcapriolo/entry/schema_vs_schema_less
Does your the tool handle the fact that foreign keys do not work? Or for
that matter, how are your dealing with the fact that a "primary key" in
cassandra is nothing like a "primary key" in a RDBMS?
Generally under th
If the syntax effectively does nothing I do not see the point of adding it.
CQL is never going to be 100% compatible ANSI-SQL dialect.
On Sat, Mar 2, 2013 at 12:19 PM, Michael Kjellman
wrote:
> Might want to create a Jira ticket at issues.apache.org instead of
> submitting the bug report thru ema
It might be reasonable to enforce length on byte and string since this is
an upper limit, but just adding it to the grammer for compatability is just
more grammer. Personally I like nosql because of the nogrammer part, CQL
create table is not toocumbersome butI dont want to jump through hoops
speci
I am curious what you mean when you say "does the fat client work right
now?"
What does not work about it? I have a fat client app running same jvm as c*
it seems to work well.
On Monday, February 25, 2013, Jonathan Ellis wrote:
> Last Thursday, DataStax put together a meeting of the active Ca
When a node is joining/bootstrapping the ring and replication factor
is 3, the write operation should be delivered to 4 nodes. The three
current natural endpoints and the new one. In this way if the joining
node fails to join the other nodes did not miss any writes.
The joining node will not answe
Counter proposal java 8 and closures. Jk
On Thursday, February 7, 2013, Carl Yeksigian wrote:
> +1
>
>
> On Wed, Feb 6, 2013 at 5:21 PM, Jonathan Ellis wrote:
>
>> Java 6 EOL is this month. Java 7 will be two years old when C* 2.0
>> comes out (July). Anecdotally, a bunch of people are running
so that
is probably where that came from)
On Wed, Jan 9, 2013 at 11:25 AM, Sylvain Lebresne wrote:
> On Wed, Jan 9, 2013 at 5:04 PM, Edward Capriolo >wrote:
>
> > Was the change well accounted for in the changes.TXT or the readme.txt?
> >
>
> The news file says:
Was the change well accounted for in the changes.TXT or the readme.txt?
It hasn't been removed, it has been renamed max_threshold and moved into
the compaction options map for CQL3 (nothing has changed for thrift or
CQL2). The CQL3 reference doc hasn't been updated correctly however, which
I'll fi
:( Seems like a good thing to have, i can figure at least one degenerate
scenario where having that helps. The first being a currupt sstable...
compaction will never be able to remove it and then each compaction will
likely try to comact it again... and fail.
On Wed, Jan 9, 2013 at 10:35 AM, Brand
remember reading this is the way google has
suggested using protobufs, mark all fields optional always for maximum
compatibility.
On Tue, Jan 1, 2013 at 2:25 PM, Jonathan Ellis wrote:
> On Tue, Jan 1, 2013 at 11:42 AM, Edward Capriolo
> wrote:
> > Question. 1.2.0-beta2
> >
>
Question. 1.2.0-beta2
Why does the thrift interface have 2 CQL methods?
CqlResult execute_cql_query(1:required binary query, 2:required
Compression compression)
throws (1:InvalidRequestException ire,
2:UnavailableException ue,
3:TimedOutException te,
4:Sc
This was discussed in one of the tickets. The problem is that CQL3's sparse
tables is it has different metadata that has NOT been added to thrift's
CFMetaData. Thus thrift is unaware of exactly how to verify the insert.
Originally it was made impossible for thrift to see a sparse table (but
that r
One thing to note. The maven repo has moved from me.prettyprint to
org.Hector-client so that should aid in your searches of the maven repo.
On Tuesday, December 4, 2012, Bisht, Jaikrit wrote:
>
> Hi,
>
> Could someone recommend the stable version of Hector libraries for
Cassandra 1.1.6?
>
> Regar
I do not understand why everyone wants to force this issue on removing
thrift. If cql, cql sparse tables and the new transport are better people
will naturally begin to use them, but as it stands now I see the it
this way:
Thrift still has more clients for more languages, thrift has more higher
le
Good idea. Lets remove thrift, CQL3 is still beta, but I am willing to
upgrade to a version that removes thrift. Then when all our clients can not
connect they will be forced to get with the program.
On Fri, Nov 30, 2012 at 5:33 PM, Jason Brown wrote:
> Hi Jonathan,
>
> I'm in favor of paying of
I have another ticket open for this.
On Sat, Nov 3, 2012 at 6:29 PM, Radim Kolar wrote:
> done
> https://issues.apache.org/jira/browse/CASSANDRA-4897
I am sure no one would have an issue with an optional findbugs target.
On Mon, Jul 30, 2012 at 10:32 AM, Radim Kolar wrote:
> was any decision about findbugs made? you do not consider code style
> recommended by findbugs as good practice which should be followed?
>
> I can submit few findbugs pat
1 - 100 of 126 matches
Mail list logo
