Re: Compund/Composite column names

Sorry, just got time to submit it. Here you go: https://issues.apache.org/jira/browse/CASSANDRA-5138 -brian --- Brian O'Neill Lead Architect, Software Development Health Market Science The Science of Better Results 2700 Horizon Drive € King of Prussia, PA € 19406 M: 215.588.6024 € @boneill42

Re: max_compaction_threshold removed - bad move

On Wed, Jan 9, 2013 at 5:30 PM, Edward Capriolo wrote: > If you want to complain about bad names in the code, start with the class > implementing keyspaces being called Table. > > OMG that is terrible! > I know!!! -- Sylvain

Re: max_compaction_threshold removed - bad move

If you want to complain about bad names in the code, start with the class implementing keyspaces being called Table. OMG that is terrible! We should only be wrongfully calling a "column family" a "table" :) (In hbase tables are actually a collection of column familes right so that is probably wh

Re: max_compaction_threshold removed - bad move

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: "CQL3 is now considered final in this release. Compared to the beta version that is part of 1.1, this final version has a few additions (collect

Re: max_compaction_threshold removed - bad move

Yikes. Please would be nice.. Also, Sylvian already said they would update the documentation. As a developer, who hasn't forgotten to update documentation? On 1/9/13 8:07 AM, "Radim Kolar" wrote: >if this was renamed then update your documentation: > >http://www.datastax.com/docs/1.2/configura

Re: max_compaction_threshold removed - bad move

if this was renamed then update your documentation: http://www.datastax.com/docs/1.2/configuration/storage_configuration

Re: max_compaction_threshold removed - bad move

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

Re: max_compaction_threshold removed - bad move

On Wed, Jan 9, 2013 at 4:21 PM, Radim Kolar wrote: > removing max_compaction_threshold in 1.2 was bad move, keeping it low > helps compaction throughput because it lowers number of disk seeks. > It hasn't been removed, it has been renamed max_threshold and moved into the compaction options map f

Re: max_compaction_threshold removed - bad move

On Wed, Jan 9, 2013 at 9:40 AM, Edward Capriolo wrote: > :( 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 coma

Re: max_compaction_threshold removed - bad move

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

Re: max_compaction_threshold removed - bad move

On Wed, Jan 9, 2013 at 9:21 AM, Radim Kolar wrote: > removing max_compaction_threshold in 1.2 was bad move, keeping it low helps > compaction throughput because it lowers number of disk seeks. :(

max_compaction_threshold removed - bad move

removing max_compaction_threshold in 1.2 was bad move, keeping it low helps compaction throughput because it lowers number of disk seeks. if you have redhat linux, check during install category "performance tools" or something like that, you will get tools for disk monitoring. Learn to use the