Lots of people thinking alike. This was just being discussed on #cassandra-dev
https://wilderness.apache.org/channels/?f=cassandra-dev/2017-09-19#1505841128
There were a couple tickets that are almost done that people wanted to get in
before we cut a patch release.
-Jeremiah
> On Sep 19, 2017,
It's been about 3 mos since our last set.
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
Hello,
In our production cluster, we had multiple times that after a *unclean*
shutdown, cassandra sever can not start due to commit log exceptions:
2017-09-17_06:06:32.49830 ERROR 06:06:32 [main]: Exiting due to error while
processing commit log during initialization.
2017-09-17_06:06:32.49831
o
4.0 should also fail startup (very early) if it still sees any non-migrated
tables, probably.
—
AY
On 19 September 2017 at 18:35:11, J. D. Jordan (jeremiah.jor...@gmail.com)
wrote:
Thanks for the clarification. +1 for adding a "DROP COMPACT STORAGE" option in
3.x and then not allowing it to b
Thanks for the clarification. +1 for adding a "DROP COMPACT STORAGE" option in
3.x and then not allowing it to be specified in 4.0.
On Sep 19, 2017, at 1:27 PM, Alex P wrote:
>> If we provide a way to drop the flag, but still access the data, I think
>> that is fine and perfectly reasonable.
> If we provide a way to drop the flag, but still access the data, I think that
> is fine and perfectly reasonable. If the proposal here is that users who
> have data in COMPACT STORAGE tables have no way to upgrade to 4.0 and still
> access that data without exporting it to a brand new table,
What's your JIRA username? I'll add you as a contributor.
(Goes for anyone - please email me directly and not spam the list)
On Tue, Sep 19, 2017 at 10:03 AM, Tyagi, Preetika
wrote:
> Thank you, Jeff. It was really helpful!
>
> Also, do I need to request an access in order to be able to assig
Thank you, Jeff. It was really helpful!
Also, do I need to request an access in order to be able to assign an issue to
myself? I cannot find an option to do that when I'm logged in.
Preetika
-Original Message-
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, September 19, 2017
If it's created by someone else but not assigned, you can assign it to
yourself and begin work
If it's created by someone else and assigned to someone else, you should
post on the ticket and ask if they mind if you work on it instead.
Sometimes people assign and then never work on it, and they won
Hi all,
I'm trying to figure out different ways in which one can contribute to
Cassandra. I know one can create a ticket and assign it to himself to work on
it. However, is it also allowed to assign and work on an already existing
ticket created by someone else?
Thanks,
Preetika
I think that all the work to support Compact Storage tables from CQL seems like
wasted effort if we are going to tell people “just kidding, you have to migrate
all your data”. I do not think supporting “COMPACT STORAGE” as a table option
matters one way or the other. But I do think being able
As you may know, SuperColumn Tables did not work in 3.x the way they worked in
2.x. In order to provide everyone with a reasonable upgrade path, we've been
working on CASSANDRA-12373[1], that brings in support for SuperColumn tables as
close to 2.x as possible. The patch is planned to land cassa
12 matches
Mail list logo