date:20110526

[jira] [Commented] (CASSANDRA-2709) sstableloader throws an exception when RF1

2011-05-26 Thread Stu Hood (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13039545#comment-13039545
 ] 

Stu Hood commented on CASSANDRA-2709:
-

Doh. That error message should read: blah blah blah CASSANDRA-2641.

 sstableloader throws an exception when RF1
 ---

 Key: CASSANDRA-2709
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2709
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Brandon Williams
Priority: Minor
 Fix For: 0.8.1


 {noformat}
 Exception in thread main java.lang.AssertionError: Overlapping ranges 
 passed to normalize: see CASSANDRA-2461: 
 (113427455640312821154458202477256070484,170141183460469231731687303715884105726]
  and 
 [(56713727820156410577229101238628035242,113427455640312821154458202477256070484]]
 at 
 org.apache.cassandra.dht.AbstractBounds.normalize(AbstractBounds.java:104)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.getPositionsForRanges(SSTableReader.java:497)
 at 
 org.apache.cassandra.streaming.StreamOut.createPendingFiles(StreamOut.java:168)
 at 
 org.apache.cassandra.streaming.StreamOut.transferSSTables(StreamOut.java:148)
 at 
 org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:128)
 at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:61)
 {noformat}
 However, it does appear to keep streaming files.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2709) sstableloader throws an exception when RF1

2011-05-26 Thread Brandon Williams (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13039547#comment-13039547
 ] 

Brandon Williams commented on CASSANDRA-2709:
-

Yeah, I already fixed that part in the 0.8 branch.

 sstableloader throws an exception when RF1
 ---

 Key: CASSANDRA-2709
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2709
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Brandon Williams
Priority: Minor
 Fix For: 0.8.1


 {noformat}
 Exception in thread main java.lang.AssertionError: Overlapping ranges 
 passed to normalize: see CASSANDRA-2461: 
 (113427455640312821154458202477256070484,170141183460469231731687303715884105726]
  and 
 [(56713727820156410577229101238628035242,113427455640312821154458202477256070484]]
 at 
 org.apache.cassandra.dht.AbstractBounds.normalize(AbstractBounds.java:104)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.getPositionsForRanges(SSTableReader.java:497)
 at 
 org.apache.cassandra.streaming.StreamOut.createPendingFiles(StreamOut.java:168)
 at 
 org.apache.cassandra.streaming.StreamOut.transferSSTables(StreamOut.java:148)
 at 
 org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:128)
 at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:61)
 {noformat}
 However, it does appear to keep streaming files.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2626) stack overflow while compacting

2011-05-26 Thread Shotaro Kamio (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shotaro Kamio updated CASSANDRA-2626:
-

Attachment: CASSANDRA-2626.patch

This patch prevents stack overflow. Apache commons UnmodifiableSet is used 
instead of java.util.Collections.UnmodifiableSet because the latter is not 
accessible due to package private.


 stack overflow while compacting
 ---

 Key: CASSANDRA-2626
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2626
 Project: Cassandra
  Issue Type: Bug
  Components: Documentation  website
Affects Versions: 0.8 beta 1
Reporter: Terje Marthinussen
Assignee: Shotaro Kamio
 Fix For: 0.8.0

 Attachments: 2626.txt, CASSANDRA-2626.patch


 This is a trunk build from May 3.
 After adding  CASSANDRA-2401, I have gotten the following on several nodes.
 I am not 100% sure right now if it is related to 2401 but it may seem likely.
 Unfortunately, as often is the case with stack overflows, I don't see the 
 start of the stack
 ERROR [CompactionExecutor:17] 2011-05-09 07:56:32,479 
 AbstractCassandraDaemon.java (line 112) Fatal exception in thread 
 Thread[CompactionExecutor:17,1,main]
 java.lang.StackOverflowError
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)
 at 
 java.util.Collections$UnmodifiableCollection.size(Collections.java:998)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2221) 'show create' commands on the CLI to export schema

2011-05-26 Thread David Boxenhorn (JIRA)

[
https://issues.apache.org/jira/browse/CASSANDRA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13039601#comment-13039601
]

David Boxenhorn commented on CASSANDRA-2221:

This looks a lot like the use case that I was trying to solve with
CASSANDRA-2636 (I didn't know about this ticket), except for one thing: I want
to either create a new cluster or update an old one (i.e. propagate *changes*
from dev). I could manually substitute update for create, but I would
prefer a solution that doesn't require human intervention. How about,
recreate, which will create the CF if it doesn't exist, otherwise update it?

'show create' commands on the CLI to export schema
--

Key: CASSANDRA-2221
URL: https://issues.apache.org/jira/browse/CASSANDRA-2221
Project: Cassandra
Issue Type: Improvement
Components: Tools
Reporter: Jeremy Hanna
Assignee: Aaron Morton
Priority: Minor
Labels: cli
Fix For: 0.8.1

Attachments: 0001-add-show-schema-statement-8.patch,
0001-add-show-schema-statement.patch

It would be nice to have 'show create' type of commands on the command-line
so that it would generate the DDL for the schema.
A scenario that would make this useful is where a team works out a data model
over time with a dev cluster. They want to use parts of that schema for new
clusters that they create, like a staging/prod cluster. It would be very
handy in this scenario to have some sort of export mechanism.
Another use case is for testing purposes - you want to replicate a problem.
We currently have schematool for import/export but that is deprecated and it
exports into yaml.
This new feature would just be able to 'show' - or export if they want the
entire keyspace - into a script or commands that could be used in a cli
script. It would need to be able to regenerate everything about the keyspace
including indexes and metadata.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2704) provide a typed key value for returned rows via JDBC

2011-05-26 Thread Aaron Morton (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Morton updated CASSANDRA-2704:


Attachment: 0001-2704.patch

I'd already written the code last night before creating the ticket,and getting 
distracted by an unhappy toddler. So I may as well add it. 

The CassandraResultSet already provides the key as a byte[], this patch makes 
it available as a typed value like the columns. Handy for times when the key 
cannot projected into the result set. 

 provide a typed key value for returned rows via JDBC
 

 Key: CASSANDRA-2704
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2704
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 0.8.0 beta 2
Reporter: Aaron Morton
Priority: Minor
 Attachments: 0001-2704.patch


 o.a.c.c.jdbc.CassandraResultSet provides access to column values as Cassandra 
 type aware via the TypedColumn. But it only provides a byte[] for the key. It 
 would be handy to have a TypedKey class that does the same but for the key.
 This would be handy when doing a multi SELECT as the server only returns rows 
 we have columns for.   

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-2710) Get multiple column ranges

2011-05-26 Thread David Boxenhorn (JIRA)

Get multiple column ranges
--

 Key: CASSANDRA-2710
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2710
 Project: Cassandra
  Issue Type: Improvement
Reporter: David Boxenhorn


I have replaced all my super column families with regular column families using 
composite columns. I have easily been able to support all previous 
functionality (I don't need range delete) except for one thing: getting 
multiple super columns with a single access. For this, I would need to get 
multiple ranges. (I can get multiple columns, or a single range, but not 
multiple ranges.) 

For example, I used to have

[superColumnName1,subColumnName1..N],[superColumnName2,subColumnName1..N]

and I could get superColumnName1, superColumnName2

Now I have

[lensuperColumnName10lensubColumnName1..lensuperColumnName10lensubColumnNameN],[lensuperColumnName20lensubColumnName1..lensuperColumnName20lensubColumnNameN]

and I need to get superColumnName1..superColumnName1+, 
superColumnName2..superColumnName2+

to get the same functionality

I would like the clients to support this functionality, e.g. Hector to have 
.setRages parallel to .setColumnNames 

and for CQL to support a syntax like 

SELECT [FIRST N] [REVERSED] name1..nameN1, name2..nameN2... FROM ...



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

48 matches

Mail list logo