[
https://issues.apache.org/jira/browse/CASSANDRA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977054#comment-13977054
]
Jason Brown edited comment on CASSANDRA-7033 at 4/22/14 5:00 PM:
-----------------------------------------------------------------
While I agree that it's harmless in this case, the authors of the library felt
otherwise about it being an anti-pattern (hence the logging). That being said
adding the following line to my conf/logback.xml shuts up the java driver
rather easily:
{code}<logger name="com.datastax.driver.core" level="ERROR"/>{code}
I'm doubtful we want to add that to the main logging file for cassandra (as it
would introduce some, albeit minor, confusion), but leaving it here for
posterity.
was (Author: jasobrown):
While I agree that it's harmless in this case, the authors of the library felt
otherwise about it being an anti-pattern (hence the logging). That being said
adding the following line to my conf/logback.xml shuts up the java driverrather
easily:
{code}<logger name="com.datastax.driver.core" level="ERROR"/>{code}
I'm doubtful we want to add that to the main logging file for cassandra (as it
would introduce some, albeit minor, confusion), but leaving it here for
posterity.
> new stress errors on reads with native protocol
> -----------------------------------------------
>
> Key: CASSANDRA-7033
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7033
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jason Brown
> Assignee: Benedict
> Priority: Minor
> Labels: native_protocol, stress
> Fix For: 2.1.0
>
> Attachments: 7033.txt
>
>
> Getting errors when performing reads on native protocol (possible due to
> using prepared statements). Generate writes with this:
> {code}
> cassandra-stress write -schema replication\(factor\=2\) -mode native prepared
> cql3 -port native=9043 thrift=9161
> {code}
> Then trying to read gives this error:
> {code}
> cassandra-stress read -schema replication\(factor\=2\) -mode native prepared
> cql3 -port native=9043 thrift=9161
> com.datastax.driver.core.exceptions.SyntaxError: line 1:7 no viable
> alternative at input '?'
> at
> com.datastax.driver.core.exceptions.SyntaxError.copy(SyntaxError.java:35)
> at
> com.datastax.driver.core.DefaultResultSetFuture.extractCauseFromExecutionException(DefaultResultSetFuture.java:256)
> at
> com.datastax.driver.core.SessionManager.prepare(SessionManager.java:110)
> at
> org.apache.cassandra.stress.util.JavaDriverClient.prepare(JavaDriverClient.java:57)
> at
> org.apache.cassandra.stress.operations.CqlOperation$JavaDriverWrapper.createPreparedStatement(CqlOperation.java:325)
> at
> org.apache.cassandra.stress.operations.CqlOperation.run(CqlOperation.java:74)
> at
> org.apache.cassandra.stress.operations.CqlOperation.run(CqlOperation.java:106)
> at
> org.apache.cassandra.stress.operations.CqlOperation.run(CqlOperation.java:269)
> at
> org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:296)
> Caused by: com.datastax.driver.core.exceptions.SyntaxError: line 1:7 no
> viable alternative at input '?'
> at
> com.datastax.driver.core.Responses$Error.asException(Responses.java:94)
> at
> com.datastax.driver.core.SessionManager$2.apply(SessionManager.java:209)
> at
> com.datastax.driver.core.SessionManager$2.apply(SessionManager.java:184)
> at com.google.common.util.concurrent.Futures$1.apply(Futures.java:713)
> at
> com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:861)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
