[jira] [Assigned] (CASSANDRA-3426) clientutil -javadoc and -sources jars

[satish babu krishnamoorthy (Assigned) (JIRA)]

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

satish babu krishnamoorthy reassigned CASSANDRA-3426:
-

Assignee: satish babu krishnamoorthy

 clientutil -javadoc and -sources jars
 -

 Key: CASSANDRA-3426
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3426
 Project: Cassandra
  Issue Type: Task
  Components: Drivers, Packaging, Tools
Affects Versions: 1.0.0
Reporter: Eric Evans
Assignee: satish babu krishnamoorthy
Priority: Minor
  Labels: lhf

 The build produces a jar of classes useful for Java clients, 
 {{apache-cassandra-clientutil-version.jar}}.  Convention dictates that 
 corresponding classes for source and documentation should also be created.
 * {{apache-cassandra-clientutil-version-javadoc.jar}}
 * {{apache-cassandra-clientutil-version-sources.jar}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-3326) Add timing information to cassandra-cli queries

[satish babu krishnamoorthy (Assigned) (JIRA)]

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

satish babu krishnamoorthy reassigned CASSANDRA-3326:
-

Assignee: satish babu krishnamoorthy

 Add timing information to cassandra-cli queries
 ---

 Key: CASSANDRA-3326
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3326
 Project: Cassandra
  Issue Type: New Feature
  Components: Tools
Reporter: Radim Kolar
Assignee: satish babu krishnamoorthy
Priority: Minor

 It would be highly helpful for monitoring cluster health to return ETA on 
 queries in cassandra-cli. MySQL is doing it too and you can switch this 
 feature on in Postgresql and Oracle CLI.
 get testdb[234123];
 Returned 0 results *in 0.08 ms*.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-3312) need initClause when catch Exception and throw new Exception in cli

[satish babu krishnamoorthy (Assigned) (JIRA)]

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

satish babu krishnamoorthy reassigned CASSANDRA-3312:
-

Assignee: satish babu krishnamoorthy  (was: Pavel Yaskevich)

 need initClause when catch Exception and throw new Exception in cli
 ---

 Key: CASSANDRA-3312
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3312
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.1
Reporter: Jackson Chung
Assignee: satish babu krishnamoorthy
Priority: Minor
 Attachments: 3312.patch


 through CASSANDRA-2746 , we added initCause to the Cli such that we could see 
 more meaningful exception stacktrace when certain exception is thrown.
 However, there are still some other area, eg:
 executeGetWithConditions(Tree)
 executeSet(Tree)
 executeIncr(Tree, long)
 etc etc...
 basically any time you do a
 {code}
 {
 throw new RuntimeException(e.getMessage());
 }
 {code}
 the real exception is lost. The right approach should be:
 {code}
 catch (Exception e)
 {
 throw new RuntimeException(e.getMessage(), e);
 }
 {code}
 eg: i was getting this:
 null
 java.lang.RuntimeException
 at 
 org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:310)
 at org.apache.cassandra.cli.CliMain.processStatement(CliMain.java:217)
 at org.apache.cassandra.cli.CliMain.main(CliMain.java:345)
 Caused by: java.lang.RuntimeException
 at 
 org.apache.cassandra.cli.CliClient.executeGetWithConditions(CliClient.java:815)
 at 
 org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:208)
 ... 2 more
 but i have no idea what the problem is with just the above stack trace.
 with the fix, this would tell us more:
 null
 java.lang.RuntimeException
 at 
 org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:310)
 at org.apache.cassandra.cli.CliMain.processStatement(CliMain.java:217)
 at org.apache.cassandra.cli.CliMain.main(CliMain.java:345)
 Caused by: java.lang.RuntimeException
 at 
 org.apache.cassandra.cli.CliClient.executeGetWithConditions(CliClient.java:815)
 at 
 org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:208)
 ... 2 more
 Caused by: UnavailableException()
 at 
 org.apache.cassandra.thrift.Cassandra$get_indexed_slices_result.read(Cassandra.java:14065)
 at 
 org.apache.cassandra.thrift.Cassandra$Client.recv_get_indexed_slices(Cassandra.java:810)
 at 
 org.apache.cassandra.thrift.Cassandra$Client.get_indexed_slices(Cassandra.java:782)
 at 
 org.apache.cassandra.cli.CliClient.executeGetWithConditions(CliClient.java:806)
 ... 3 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira