[Cassandra Wiki] Update of "NodeProbe" by JoaquinCasares
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for
change notification.
The "NodeProbe" page has been changed by JoaquinCasares.
The comment on this change is: Added a comment about the deletion of compacted
tables requiring the jvm's GC..
http://wiki.apache.org/cassandra/NodeProbe?action=diff&rev1=11&rev2=12
--
bin/nodetool -host 10.176.0.146 cleanup
}}}
== Compact ==
- Initiates an immediate table compaction.
+ Initiates an immediate table compaction.
+
+ Note: the compacted tables will not immediately be cleared from the hard disk
and will remain on the system until the JVM performs a GC. For more
information, read about
[[http://wiki.apache.org/cassandra/MemtableSSTable|MemtableSSTables]].
{{{
bin/nodetool -host 10.176.0.146 compact
[jira] Commented: (CASSANDRA-2277) parameter substitution for Java CQL driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003274#comment-13003274
]
Vivek Mishra commented on CASSANDRA-2277:
-
Can we link it with Cassandra-2124?
> parameter substitution for Java CQL driver
> --
>
> Key: CASSANDRA-2277
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2277
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
>Reporter: Eric Evans
> Labels: cql
> Fix For: 0.8
>
>
> The Java driver should support parameter substitution such that given a query
> string and a sequence of arguments, question marks ('?') in the query string
> will be substituted with the arguments.
> {code:style=Java}
> conn.execute("SELECT ?,? FROM Standard1 WHERE KEY = ?", 10, 20, "foo")
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2277) parameter substitution for Java CQL driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003273#comment-13003273
]
Vivek Mishra commented on CASSANDRA-2277:
-
Eric,
I can take up this one. Possible to assign to me?
Vivek
> parameter substitution for Java CQL driver
> --
>
> Key: CASSANDRA-2277
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2277
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
>Reporter: Eric Evans
> Labels: cql
> Fix For: 0.8
>
>
> The Java driver should support parameter substitution such that given a query
> string and a sequence of arguments, question marks ('?') in the query string
> will be substituted with the arguments.
> {code:style=Java}
> conn.execute("SELECT ?,? FROM Standard1 WHERE KEY = ?", 10, 20, "foo")
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2088) Temp files for failed compactions/streaming not cleaned up
[ https://issues.apache.org/jira/browse/CASSANDRA-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003264#comment-13003264 ] Aaron Morton commented on CASSANDRA-2088: - I'm keen to try this ticket (to learn more about compaction and repair) if it's not already been worked on. Also if it's ok for me to take a couple of days while I dig into this. For compaction I'm looking in - CompactionManager.doCompaction where it creates a new SSTableWriter via cfs.createCompactionWriter() - CompactionManager.doCleanupCompaction() also uses an SSTableWriter Are the sorts of failures we're considering for compaction ones that come from the CompactionIterator or SSTableScanner ? For repair I'm looking in: - IncomingStreamReader appears to clean up the temporary pending file in some error situations. Do we have any more info on the sorts of failures here? e.g. If there is an IOException sending the re-stream message, or a non checked exception it will fail to cleaup the file. - I'm looking into what happens in StreamInSession.finished() closeIfFinished() - Are we considering failures during the streaming or when processing the data after the stream has finished? Any guidance welcome. > Temp files for failed compactions/streaming not cleaned up > -- > > Key: CASSANDRA-2088 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2088 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Stu Hood > Fix For: 0.7.4 > > > From separate reports, compaction and repair are currently missing > opportunities to clean up tmp files after failures. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Cassandra Wiki] Update of "API" by TylerHobbs
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification. The "API" page has been changed by TylerHobbs. The comment on this change is: Remove duplicate (and incorrect) describe_keyspaces() entry. http://wiki.apache.org/cassandra/API?action=diff&rev1=20&rev2=21 -- Remove data from the row specified by `key` at the granularity specified by `column_path`, and the given `timestamp`. Note that all the values in `column_path` besides `column_path.column_family` are truly optional: you can remove the entire row by just specifying the !ColumnFamily, or you can remove a !SuperColumn or a single Column by specifying those levels too. Note that the `timestamp` is needed, so that if the commands are replayed in a different order on different nodes, the same result is produced. + === truncate === - === describe_keyspaces === - . `set describe_keyspaces()` - Gets a list of all the keyspaces configured for the cluster. + . `truncate(string column_family)` + + Removes all the rows from the given column family. === describe_cluster_name === . `string describe_cluster_name()` Gets the name of the cluster. + === describe_keyspace === + + . `KsDef describe_keyspace(string keyspace)` + + Gets information about the specified keyspace. + + === describe_keyspaces === + + . `list describe_keyspaces()` + + Gets a list of all the keyspaces configured for the cluster. (Equivalent to calling describe_keyspace(k) for k in keyspaces.) + === describe_partitioner === . `string describe_partitioner()` @@ -302, +315 @@ Gets the Thrift API version. - === describe_keyspace === - - . `KsDef describe_keyspace(string keyspace)` - - Gets information about the specified keyspace. - - === describe_keyspaces === - - . `list describe_keyspaces()` - - Gets a list of all the keyspaces configured for the cluster. (Equivalent to calling describe_keyspace(k) for k in keyspaces.) - - === truncate === - - . `truncate(string column_family)` - - Removes all the rows from the given column family. - === system_add_column_family === . `string system_add_column_family(CFDef cf_def)`
[Cassandra Wiki] Update of "API" by TylerHobbs
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification. The "API" page has been changed by TylerHobbs. The comment on this change is: Added describe_snitch(). http://wiki.apache.org/cassandra/API?action=diff&rev1=19&rev2=20 -- Gets the name of the cluster. + === describe_partitioner === + . `string describe_partitioner()` + + Gets the name of the partitioner for the cluster. + + === describe_ring === + . `list describe_ring(keyspace)` + + Gets the token ring; a map of ranges to host addresses. Represented as a set of `TokenRange` instead of a map from range to list of endpoints, because you can't use Thrift structs as map keys: https://issues.apache.org/jira/browse/THRIFT-162 for the same reason, we can't return a set here, even though order is neither important nor predictable. + + === describe_snitch === + . `string describe_snitch()` + + Gets the name of the snitch used for the cluster. + === describe_version === . `string describe_version()` Gets the Thrift API version. - === describe_ring === - . `list describe_ring(keyspace)` - - Gets the token ring; a map of ranges to host addresses. Represented as a set of `TokenRange` instead of a map from range to list of endpoints, because you can't use Thrift structs as map keys: https://issues.apache.org/jira/browse/THRIFT-162 for the same reason, we can't return a set here, even though order is neither important nor predictable. - - === describe_partitioner === - . `string describe_partitioner()` - - Gets the name of the partitioner for the cluster. - === describe_keyspace === . `KsDef describe_keyspace(string keyspace)`
[Cassandra Wiki] Update of "API" by TylerHobbs
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification. The "API" page has been changed by TylerHobbs. The comment on this change is: Added describe_partitioner(). http://wiki.apache.org/cassandra/API?action=diff&rev1=18&rev2=19 -- Gets the token ring; a map of ranges to host addresses. Represented as a set of `TokenRange` instead of a map from range to list of endpoints, because you can't use Thrift structs as map keys: https://issues.apache.org/jira/browse/THRIFT-162 for the same reason, we can't return a set here, even though order is neither important nor predictable. + === describe_partitioner === + . `string describe_partitioner()` + + Gets the name of the partitioner for the cluster. + === describe_keyspace === . `KsDef describe_keyspace(string keyspace)`
[jira] Updated: (CASSANDRA-2008) CLI help incorrect in places
[ https://issues.apache.org/jira/browse/CASSANDRA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Morton updated CASSANDRA-2008: Attachment: 2008-2.patch Second patch includes all the stuff from first patch and adds CounterColumnType to the help. Against the 0.8 trunk > CLI help incorrect in places > > > Key: CASSANDRA-2008 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2008 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 0.8 >Reporter: Aaron Morton >Assignee: Aaron Morton >Priority: Trivial > Fix For: 0.8 > > Attachments: 2007.txt, 2008-2.patch > > > Found some errors in the CLI help, such as these for create column family. > - memtable_operations: Flush memtables after this many operations > - memtable_throughput: ... or after this many bytes have been written > - memtable_flush_after: ... or after this many seconds > Should be millions of ops, MB's written and minutes not seconds. Have > confirmed thats how the values are used. Will check all the help. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CASSANDRA-2007) Move demo Keyspace1 definition from casandra.yaml to an input file for cassandra-cli
[ https://issues.apache.org/jira/browse/CASSANDRA-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Morton updated CASSANDRA-2007: Affects Version/s: (was: 0.7.0) 0.8 Fix Version/s: (was: 0.7.4) 0.8 > Move demo Keyspace1 definition from casandra.yaml to an input file for > cassandra-cli > > > Key: CASSANDRA-2007 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2007 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 0.8 >Reporter: Aaron Morton >Assignee: Aaron Morton >Priority: Trivial > Fix For: 0.8 > > Attachments: 2007-1.patch, 2007-2.patch > > > Th suggested way to make schema changes is through cassandra-cli but we do > not have an example of how to do it. Additionally, to get the demo keyspace > created users have to use a different process. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CASSANDRA-2007) Move demo Keyspace1 definition from casandra.yaml to an input file for cassandra-cli
[ https://issues.apache.org/jira/browse/CASSANDRA-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Morton updated CASSANDRA-2007: Attachment: 2007-2.patch 2007-2.patch is a rebased version against the trunk @ 8fa4253. The schema includes the counter examples. All help has been removed from the example schema as help has been added to the cli in CASSANDRA-2008. There are also changes to handle keyspaces: not been present in the yaml when loadSchemaFromYaml is called. The patch is intended for v0.8 as it is not a bug fix. Let me know if we would also like it against 0.7. > Move demo Keyspace1 definition from casandra.yaml to an input file for > cassandra-cli > > > Key: CASSANDRA-2007 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2007 > Project: Cassandra > Issue Type: Improvement > Components: Core >Affects Versions: 0.8 >Reporter: Aaron Morton >Assignee: Aaron Morton >Priority: Trivial > Fix For: 0.8 > > Attachments: 2007-1.patch, 2007-2.patch > > > Th suggested way to make schema changes is through cassandra-cli but we do > not have an example of how to do it. Additionally, to get the demo keyspace > created users have to use a different process. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (CASSANDRA-1472) Add bitmap secondary indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003216#comment-13003216 ] Stu Hood edited comment on CASSANDRA-1472 at 3/6/11 10:18 PM: -- tjake: Yea: opening a separate ticket to discuss a generic file format makes sense. I had a realization about this implementation of secondary indexes: I was originally thinking we'd be able to push all boolean queries down to the indexes on a per-sstable basis, but this is unfortunately not the case. We will not be able to push 'AND' on separate indexes down to the sstables themselves: we'd need to join the index from all sstables, since a row might contain one clause in one sstable, and another clause in another sstable. EDIT: This is roughly equivalent to what we'd need to do with a KEYS index (seek-wise), meaning that the advantage is mostly in space utilization and lack of locks. was (Author: stuhood): tjake: Yea: opening a separate ticket to discuss a generic file format makes sense. I had a realization about this implementation of secondary indexes: I was originally thinking we'd be able to push all boolean queries down to the indexes on a per-sstable basis, but this is unfortunately not the case. We will not be able to push 'AND' on separate indexes down to the sstables themselves: we'd need to join the index from all sstables, since a row might contain one clause in one sstable, and another clause in another sstable. > Add bitmap secondary indexes > > > Key: CASSANDRA-1472 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1472 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Stu Hood >Assignee: Stu Hood > Fix For: 0.7.4 > > Attachments: 0.7-1472-v5.tgz, 0.7-1472-v6.tgz, > 0001-CASSANDRA-1472-rebased-to-0.7-branch.txt, > 0019-Rename-bugfixes-and-fileclose.txt, 1472-v3.tgz, 1472-v4.tgz, > 1472-v5.tgz, anatomy.png, v4-bench-c32.txt > > > Bitmap indexes are a very efficient structure for dealing with immutable > data. We can take advantage of the fact that SSTables are immutable by > attaching them directly to SSTables as a new component (supported by > CASSANDRA-1471). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-1472) Add bitmap secondary indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003216#comment-13003216 ] Stu Hood commented on CASSANDRA-1472: - tjake: Yea: opening a separate ticket to discuss a generic file format makes sense. I had a realization about this implementation of secondary indexes: I was originally thinking we'd be able to push all boolean queries down to the indexes on a per-sstable basis, but this is unfortunately not the case. We will not be able to push 'AND' on separate indexes down to the sstables themselves: we'd need to join the index from all sstables, since a row might contain one clause in one sstable, and another clause in another sstable. > Add bitmap secondary indexes > > > Key: CASSANDRA-1472 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1472 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Stu Hood >Assignee: Stu Hood > Fix For: 0.7.4 > > Attachments: 0.7-1472-v5.tgz, 0.7-1472-v6.tgz, > 0001-CASSANDRA-1472-rebased-to-0.7-branch.txt, > 0019-Rename-bugfixes-and-fileclose.txt, 1472-v3.tgz, 1472-v4.tgz, > 1472-v5.tgz, anatomy.png, v4-bench-c32.txt > > > Bitmap indexes are a very efficient structure for dealing with immutable > data. We can take advantage of the fact that SSTables are immutable by > attaching them directly to SSTables as a new component (supported by > CASSANDRA-1471). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CASSANDRA-2278) CLI list fails when keys are not of the assumed type
CLI list fails when keys are not of the assumed type
-
Key: CASSANDRA-2278
URL: https://issues.apache.org/jira/browse/CASSANDRA-2278
Project: Cassandra
Issue Type: Bug
Components: Tools
Affects Versions: 0.7.3
Reporter: Yaniv Kunda
Priority: Minor
If a keyspace contains non-utf8 keys (for example, {{LongType}} keys), the
"{{list ;}}" command can fail converting a key for display, only outputting
the message "{{Input length = 1}}" and stopping the listing of the rest of the
keys.
This message seems to be an example of the standard exception message of
{{java.nio.charset.MalformedInputException}}.
Similar messages will probably appear when utf8 keys are assumed to be long,
etc.
Workaround: use "{{assume keys as ;}}" - but this will work only of
all displayed keys conform to the assumption type.
Suggested fix: If key cannot be converted to the assumption type, instead of
{{RowKey: }}
display
{{RowKey bytes: (cannot convert key to )}}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
