date:20131111

[jira] [Created] (CASSANDRA-6329) example pig script doesn't run

2013-11-11 Thread Jeremy Hanna (JIRA)

Jeremy Hanna created CASSANDRA-6329:
---

 Summary: example pig script doesn't run
 Key: CASSANDRA-6329
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6329
 Project: Cassandra
  Issue Type: Bug
  Components: Hadoop
Reporter: Jeremy Hanna
Priority: Trivial


The following line in the examples/pig/example-script.pig will not run (using 
Pig 0.9.2):
{code}
state_footage = FOREACH state_grouped GENERATE GROUP AS State, 
SUM(state_flat.SquareFeet) AS TotalFeet:int;
{code}

It needs to have a lowercase 'group' because that's the variable name after 
doing the GROUP operation in the previous line:
{code}
state_footage = FOREACH state_grouped GENERATE group AS State, 
SUM(state_flat.SquareFeet) AS TotalFeet:int;
{code}

Also, I wonder if it would be good to separate the CassandraStorage and 
CqlStorage into two different scripts, just so you can run the CqlStorage 
example out of the box without having to comment out the CassandraStorage 
example.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CASSANDRA-6316) json2sstable breaks on RangeTombstone

2013-11-11 Thread Lyuben Todorov (JIRA)


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

Lyuben Todorov commented on CASSANDRA-6316:
---

When SSTableImport#JsonColumn tries to find the comparator for the tombstoned 
range it fails and defaults to a BytesType comparator. I special-cased the 
tombstoned columns to get their comparator from the 1st component of the cf. 
[Gist of the schemas used for 
verification|https://gist.github.com/lyubent/7415048].

 json2sstable breaks on RangeTombstone
 -

 Key: CASSANDRA-6316
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6316
 Project: Cassandra
  Issue Type: Bug
 Environment: 1.2.10
Reporter: Matt Jurik
Assignee: Lyuben Todorov
Priority: Minor

 It seems that sstable2json writes out json which json2sstable has trouble 
 reading.
 {code}
 java.lang.NumberFormatException: An hex string representing bytes must have 
 an even length
   at org.apache.cassandra.utils.Hex.hexToBytes(Hex.java:52)
   at 
 org.apache.cassandra.utils.ByteBufferUtil.hexToBytes(ByteBufferUtil.java:503)
   at 
 org.apache.cassandra.tools.SSTableImport.stringAsType(SSTableImport.java:572)
   at 
 org.apache.cassandra.tools.SSTableImport.access$000(SSTableImport.java:66)
   at 
 org.apache.cassandra.tools.SSTableImport$JsonColumn.init(SSTableImport.java:158)
   at 
 org.apache.cassandra.tools.SSTableImport.addColumnsToCF(SSTableImport.java:229)
   at 
 org.apache.cassandra.tools.SSTableImport.addToStandardCF(SSTableImport.java:212)
   at 
 org.apache.cassandra.tools.SSTableImport.importUnsorted(SSTableImport.java:361)
   at 
 org.apache.cassandra.tools.SSTableImport.importJson(SSTableImport.java:318)
   at org.apache.cassandra.tools.SSTableImport.main(SSTableImport.java:537)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
 ERROR: An hex string representing bytes must have an even length
 12345:2:!
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CASSANDRA-6316) json2sstable breaks on RangeTombstone

2013-11-11 Thread Lyuben Todorov (JIRA)


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

Lyuben Todorov updated CASSANDRA-6316:
--

Attachment: 6316.diff

 json2sstable breaks on RangeTombstone
 -

 Key: CASSANDRA-6316
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6316
 Project: Cassandra
  Issue Type: Bug
 Environment: 1.2.10
Reporter: Matt Jurik
Assignee: Lyuben Todorov
Priority: Minor
 Attachments: 6316.diff


 It seems that sstable2json writes out json which json2sstable has trouble 
 reading.
 {code}
 java.lang.NumberFormatException: An hex string representing bytes must have 
 an even length
   at org.apache.cassandra.utils.Hex.hexToBytes(Hex.java:52)
   at 
 org.apache.cassandra.utils.ByteBufferUtil.hexToBytes(ByteBufferUtil.java:503)
   at 
 org.apache.cassandra.tools.SSTableImport.stringAsType(SSTableImport.java:572)
   at 
 org.apache.cassandra.tools.SSTableImport.access$000(SSTableImport.java:66)
   at 
 org.apache.cassandra.tools.SSTableImport$JsonColumn.init(SSTableImport.java:158)
   at 
 org.apache.cassandra.tools.SSTableImport.addColumnsToCF(SSTableImport.java:229)
   at 
 org.apache.cassandra.tools.SSTableImport.addToStandardCF(SSTableImport.java:212)
   at 
 org.apache.cassandra.tools.SSTableImport.importUnsorted(SSTableImport.java:361)
   at 
 org.apache.cassandra.tools.SSTableImport.importJson(SSTableImport.java:318)
   at org.apache.cassandra.tools.SSTableImport.main(SSTableImport.java:537)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
 ERROR: An hex string representing bytes must have an even length
 12345:2:!
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CASSANDRA-6316) json2sstable breaks on RangeTombstone

2013-11-11 Thread Jonathan Ellis (JIRA)


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

Jonathan Ellis updated CASSANDRA-6316:
--

 Reviewer: Aleksey Yeschenko
Reproduced In: 2.0.2, 1.2.11  (was: 1.2.11, 2.0.2)

 json2sstable breaks on RangeTombstone
 -

 Key: CASSANDRA-6316
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6316
 Project: Cassandra
  Issue Type: Bug
 Environment: 1.2.10
Reporter: Matt Jurik
Assignee: Lyuben Todorov
Priority: Minor
 Attachments: 6316.diff


 It seems that sstable2json writes out json which json2sstable has trouble 
 reading.
 {code}
 java.lang.NumberFormatException: An hex string representing bytes must have 
 an even length
   at org.apache.cassandra.utils.Hex.hexToBytes(Hex.java:52)
   at 
 org.apache.cassandra.utils.ByteBufferUtil.hexToBytes(ByteBufferUtil.java:503)
   at 
 org.apache.cassandra.tools.SSTableImport.stringAsType(SSTableImport.java:572)
   at 
 org.apache.cassandra.tools.SSTableImport.access$000(SSTableImport.java:66)
   at 
 org.apache.cassandra.tools.SSTableImport$JsonColumn.init(SSTableImport.java:158)
   at 
 org.apache.cassandra.tools.SSTableImport.addColumnsToCF(SSTableImport.java:229)
   at 
 org.apache.cassandra.tools.SSTableImport.addToStandardCF(SSTableImport.java:212)
   at 
 org.apache.cassandra.tools.SSTableImport.importUnsorted(SSTableImport.java:361)
   at 
 org.apache.cassandra.tools.SSTableImport.importJson(SSTableImport.java:318)
   at org.apache.cassandra.tools.SSTableImport.main(SSTableImport.java:537)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
 ERROR: An hex string representing bytes must have an even length
 12345:2:!
 {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CASSANDRA-6268) Poor performance of Hadoop if any DC is using VNodes

2013-11-11 Thread Jonathan Ellis (JIRA)


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

Jonathan Ellis commented on CASSANDRA-6268:
---

So I'm back to bumping to 19.36.2 and 19.39.0 as the best option.

 Poor performance of Hadoop if any DC is using VNodes
 

 Key: CASSANDRA-6268
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6268
 Project: Cassandra
  Issue Type: Improvement
  Components: Hadoop
Reporter: Piotr Kołaczkowski
Assignee: Piotr Kołaczkowski
 Attachments: 6268-src-1.2.txt, 6268-src-2.0.txt, 6268-thrift-1.2.txt, 
 6268-thrift-2.0.txt


 Some customers are complaining about huge number of splits in Hadoop caused 
 by VNodes. Disabling vnodes only in Hadoop DC does not fix it. Splits are 
 generated from the results of describe_ring, which returns a huge number of 
 ranges anyways, and doesn't take into account that there will be huge number 
 of consecutive ranges residing on the nodes we'd like the M/R job to be run.
 The proposed fix:
 1. allows for specifying the DC(s) the Hadoop job should be run in (in DSE - 
 defaults to all Hadoop DCs)
 2. merges consecutive ranges before generating Hadoop splits, so we don't 
 have artificial range splitting caused by vnodes in the other DCs
 For non-DSE users this feature is turned off by default and doesn't change 
 the old behaviour.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CASSANDRA-6268) Poor performance of Hadoop if any DC is using VNodes

2013-11-11 Thread Jeremiah Jordan (JIRA)

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

Jeremiah Jordan commented on CASSANDRA-6268:

bq. So I'm back to bumping to 19.36.2 and 19.39.0 as the best option.

+1 to those. I think those are the least likely to cause issues. And if we
change something for 2.1, we should bump the version by 3 or something, to
leave some extra numbers for 2.0.

Poor performance of Hadoop if any DC is using VNodes

Key: CASSANDRA-6268
URL: https://issues.apache.org/jira/browse/CASSANDRA-6268
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Reporter: Piotr Kołaczkowski
Assignee: Piotr Kołaczkowski
Attachments: 6268-src-1.2.txt, 6268-src-2.0.txt, 6268-thrift-1.2.txt,
6268-thrift-2.0.txt

Some customers are complaining about huge number of splits in Hadoop caused
by VNodes. Disabling vnodes only in Hadoop DC does not fix it. Splits are
generated from the results of describe_ring, which returns a huge number of
ranges anyways, and doesn't take into account that there will be huge number
of consecutive ranges residing on the nodes we'd like the M/R job to be run.
The proposed fix:
1. allows for specifying the DC(s) the Hadoop job should be run in (in DSE -
defaults to all Hadoop DCs)
2. merges consecutive ranges before generating Hadoop splits, so we don't
have artificial range splitting caused by vnodes in the other DCs
For non-DSE users this feature is turned off by default and doesn't change
the old behaviour.

52 matches

Mail list logo