On Jun 14, 2010, at Mon Jun 14, 10:45 AM, Jonathan Ellis wrote:
>>
>> I already have automation, whats missing are the details of the exact steps
>> I need to automate to accomplish the schema modification on a live cluster.
>> Even the FAQ just points to the feature in 0.7 trunk.
>
> Huh? h
On Mon, Jun 14, 2010 at 7:27 AM, Matthew Conway wrote:
>
> On Jun 13, 2010, at Sun Jun 13, 9:34 PM, Benjamin Black wrote:
>
>> On Sun, Jun 13, 2010 at 5:58 PM, Matthew Conway wrote:
>>> The ability to dynamically add new column families. Our app is currently
>>> under heavy development, and we
On Jun 13, 2010, at Sun Jun 13, 9:34 PM, Benjamin Black wrote:
> On Sun, Jun 13, 2010 at 5:58 PM, Matthew Conway wrote:
>> The ability to dynamically add new column families. Our app is currently
>> under heavy development, and we will be adding new column families at least
>> once a week aft
On Sun, Jun 13, 2010 at 5:58 PM, Matthew Conway wrote:
> The ability to dynamically add new column families. Our app is currently
> under heavy development, and we will be adding new column families at least
> once a week after we have shipped the initial production app. From the
> existing do
The ability to dynamically add new column families. Our app is currently under
heavy development, and we will be adding new column families at least once a
week after we have shipped the initial production app. From the existing docs,
it seemed to me that the procedure for changing schema in 0.
What specifically is driving you to use trunk rather than the stable,
0.6 branch?
On Sun, Jun 13, 2010 at 1:37 PM, Matthew Conway wrote:
> Not so much worried about temporary breakages, but more about design
> decisions that are made to enhance cassandra at the cost of a data format
> change.
Not so much worried about temporary breakages, but more about design decisions
that are made to enhance cassandra at the cost of a data format change. So
long as the policy here is to preserve backwards compatibility with the on disk
storage format (possibly with an automatic conversion), even
If you're comfortable following comm...@cassandra.apache.org, it
should be pretty obvious which changes are going to break things
temporarily or require a commitlog drain. Otherwise, we recommend
sticking with the stable branch until a beta is released.
On Fri, Jun 11, 2010 at 2:24 PM, Matthew Co
Hi All,
I'd like to start using trunk for something real, but am concerned about
stability of the data format. That is, will I be able to upgrade a running
system to a newer version of trunk and eventually to the 7.0 release, or are
there any changes planned to the format of the data stored on
