You can build the latest version from master but it should also work with
release version 0.5.6, just verify the jar files in interpreter/cassandra
folder

On Mon, May 9, 2016 at 8:56 PM, Kyle Burke <kyle.bu...@ignitionone.com>
wrote:

> DuyHai,
>     It looks like you’re using 0.6.0 version and I’m using 0.5.6. Sounds
> like I need to build the latest version.
>
> Respectfully,
>
> *Kyle Burke *| Data Science Engineer
> *IgnitionOne - *Marketing Technology. Simplified.
> Office: 1545 Peachtree St NE, Suite 500 | Atlanta, GA | 30309
> Direct: 404.961.3918
>
>
> From: DuyHai Doan
> Reply-To: "users@zeppelin.incubator.apache.org"
> Date: Monday, May 9, 2016 at 2:13 PM
>
> To: "users@zeppelin.incubator.apache.org"
> Subject: Re: cassandra interpreter
>
>
> 1. You don't have to add the driver jar to interpreter/cassandra folder,
> it should be there already.
>
> Here is my interpreter/cassandra folder content:
>
>  cassandra-driver-core-3.0.0-rc1.jar
>  commons-lang3-3.3.2.jar
>  guava-16.0.1.jar
>  lz4-1.3.0.jar
>  metrics-core-3.1.2.jar
>  netty-buffer-4.0.33.Final.jar
>  netty-codec-4.0.33.Final.jar
>  netty-common-4.0.33.Final.jar
>  netty-handler-4.0.33.Final.jar
>  netty-transport-4.0.33.Final.jar
>  scala-compiler-2.10.4.jar
>  scala-library-2.10.4.jar
>  scala-reflect-2.10.4.jar
>  scalate-core_2.10-1.7.1.jar
>  scalate-util_2.10-1.7.1.jar
>  slf4j-api-1.7.10.jar
>  snappy-java-1.0.5.4.jar
>  zeppelin-cassandra-0.6.0-incubating-SNAPSHOT.jar
>
> What is the content of your interpreter/cassandra folder ?
>
> 2. You don't have to add the property "cassandra.driver.version".  What
> is the value of the property "cassandra.protocol.version" for Cassandra
> interpreter ?
>
> The exception stack trace seems to show that you don't have the correct
> Java driver jar
>
>
>
>
> On Mon, May 9, 2016 at 6:04 PM, Kyle Burke <kyle.bu...@ignitionone.com>
> wrote:
>
>> Hey DuyHai,
>>    I’m still not able to use the cassandra interpreter. I’ve perform that
>> following setup tasks. I’m not sure if I missing something. Any suggestions
>> on how to correct?
>>
>>
>>    1. I added the 3.0.0-rc1 cassandra driver to the
>>    interpreter/cassandra folder.
>>    2. On the interpreter page I’ve updated the cassandra interpreter
>>    properties with a cassandra.driver.version name property and a value
>>    of 3.0.0-rc1.
>>    3. I restarted the zepellin daemon. When I do a simple “DESCRIBE
>>    KEYSPACES;” I get an error.  Below is the stack from the cassandra
>>    interpreter log.
>>
>>
>>
>> DESCRIBE KEYSPACES;
>>
>>
>> ERROR [2016-05-09 13:53:36,598] ({pool-2-thread-2} Job.java[run]:182) -
>> Job failed
>>
>> java.lang.NoSuchMethodError:
>> com.datastax.driver.core.ProtocolOptions.getProtocolVersionEnum()Lcom/datastax/driver/core/ProtocolVersion;
>>
>>         at
>> org.apache.zeppelin.cassandra.InterpreterLogic.interpret(InterpreterLogic.scala:103)
>>
>>         at
>> org.apache.zeppelin.cassandra.CassandraInterpreter.interpret(CassandraInterpreter.java:304)
>>
>>         at
>> org.apache.zeppelin.interpreter.ClassloaderInterpreter.interpret(ClassloaderInterpreter.java:57)
>>
>>         at
>> org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:93)
>>
>>         at
>> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:300)
>>
>>         at org.apache.zeppelin.scheduler.Job.run(Job.java:169)
>>
>>         at
>> org.apache.zeppelin.scheduler.ParallelScheduler$JobRunner.run(ParallelScheduler.java:157)
>>
>>         at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>
>>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>
>>         at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>>
>>         at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>>
>>         at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>
>>         at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>
>>         at java.lang.Thread.run(Thread.java:745)
>>
>>  INFO [2016-05-09 13:53:36,604] ({pool-2-thread-2}
>> SchedulerFactory.java[jobFinished]:135) - Job
>> remoteInterpretJob_1462802013711 finished by scheduler
>> org.apache.zeppelin.cassandra.CassandraInterpreter148$
>>
>>  INFO [2016-05-09 13:56:55,582] ({Thread-0}
>> RemoteInterpreterServer.java[run]:97) - Starting remote interpreter server
>> on port 54741
>>
>>  INFO [2016-05-09 13:56:55,925] ({pool-1-thread-2}
>> CassandraInterpreter.java[<clinit>]:154) - Bootstrapping Cassandra
>> Interpreter
>>
>>  INFO [2016-05-09 13:56:55,927] ({pool-1-thread-2}
>> RemoteInterpreterServer.java[createInterpreter]:168) - Instantiate
>> interpreter org.apache.zeppelin.cassandra.CassandraInterpreter
>>
>>  INFO [2016-05-09 13:56:55,977] ({pool-2-thread-2}
>> SchedulerFactory.java[jobStarted]:129) - Job
>> remoteInterpretJob_1462802215975 started by scheduler
>> org.apache.zeppelin.cassandra.CassandraInterpreter12904$
>>
>>  INFO [2016-05-09 13:56:55,978] ({pool-2-thread-2}
>> CassandraInterpreter.java[open]:268) - Bootstrapping Cassandra Java Driver
>> to connect to 10.205.33.12,10.205.43.59,on port 9042
>>
>>  INFO [2016-05-09 13:56:56,194] ({pool-2-thread-2}
>> NettyUtil.java[<clinit>]:83) - Did not find Netty's native epoll transport
>> in the classpath, defaulting to NIO.
>>
>>  INFO [2016-05-09 13:56:56,600] ({pool-2-thread-2}
>> DCAwareRoundRobinPolicy.java[init]:95) - Using data-center name 'us-east'
>> for DCAwareRoundRobinPolicy (if this is incorrect, please provide the
>> correct da$
>>
>>  INFO [2016-05-09 13:56:56,601] ({pool-2-thread-2}
>> Cluster.java[init]:1443) - New Cassandra host /X.X.X.X:9042 added
>>
>>  INFO [2016-05-09 13:56:56,601] ({pool-2-thread-2}
>> Cluster.java[init]:1443) - New Cassandra host /X.X.X.X:9042 added
>>
>>  INFO [2016-05-09 13:56:56,601] ({pool-2-thread-2}
>> Cluster.java[init]:1443) - New Cassandra host /127.0.0.1:9042 added
>>
>>  INFO [2016-05-09 13:56:56,601] ({pool-2-thread-2}
>> Cluster.java[init]:1443) - New Cassandra host /X.X.X.X:9042 added
>>
>> Respectfully,
>>
>> *Kyle Burke *| Data Science Engineer
>> *IgnitionOne - *Marketing Technology. Simplified.
>> Office: 1545 Peachtree St NE, Suite 500 | Atlanta, GA | 30309
>>
>>
>> From: DuyHai Doan
>> Reply-To: "users@zeppelin.incubator.apache.org"
>> Date: Sunday, May 8, 2016 at 3:51 AM
>> To: "users@zeppelin.incubator.apache.org"
>> Subject: Re: cassandra interpreter
>>
>> The Cassandra interpreter supports all Cassandra 3.x branch, it is using
>> the driver version <cassandra.driver.version>3.0.0-rc1</cassandra
>> .driver.version>
>>
>> I will update the interpreter soon to upgrade driver version to 3.0.0
>>
>> On Sun, May 8, 2016 at 5:38 AM, Kyle Burke <kyle.bu...@ignitionone.com>
>> wrote:
>>
>>> Hi DuyHai,
>>>    Does the Cassandra interpreter support Cassandra 3.5? The system
>>> table error I’m getting leads me to believe it’s not.
>>>
>>> Respectfully,
>>>
>>> *Kyle Burke *| Data Science Engineer
>>> *IgnitionOne - *Marketing Technology. Simplified.
>>> Office: 1545 Peachtree St NE, Suite 500 | Atlanta, GA | 30309
>>>
>>>
>>> From: DuyHai Doan
>>> Reply-To: "users@zeppelin.incubator.apache.org"
>>> Date: Friday, May 6, 2016 at 7:32 AM
>>> To: "users@zeppelin.incubator.apache.org"
>>> Subject: Re: cassandra interpreter
>>>
>>> Hello
>>>
>>> No you're mistaking, the Cassandra interpreter is only using the binary
>>> protocol to communicate with Cassandra (port 9042 by default). In the logs,
>>> what you see is the Thrift protocol used by Zeppelin to communicate between
>>> the Zeppelin server and the interpreter JVM process.
>>>
>>> By the way can you please copy/paste the complete stack trace so we can
>>> track down the root cause ?
>>>
>>>
>>> On Fri, May 6, 2016 at 12:50 AM, Kyle Burke <kyle.bu...@ignitionone.com>
>>> wrote:
>>>
>>>> All,
>>>>   I’m having connection issues trying to get zeppelin to connect to our
>>>> Cassandra cluster. Below is the error I’m getting. I’m assuming from the
>>>> error that Zeppelin uses the thrift api to connect to Cassandra. My thrift
>>>> port 9160 is open (based on netstat) so I can't seem to figure out why the
>>>> connection is refused. Any suggestions on what to test or changes required
>>>> in the cassandra config files to successfully connect would be appreciated.
>>>>
>>>>
>>>> ERROR [2016-05-05 22:29:16,939] ({pool-1-thread-2} Job.java[run]:182) -
>>>> Job failed
>>>>
>>>> org.apache.zeppelin.interpreter.InterpreterException:
>>>> org.apache.zeppelin.interpreter.InterpreterException:
>>>> org.apache.thrift.transport.TTransportException: java.net.ConnectException:
>>>> Connection refused
>>>>
>>>>         at
>>>> org.apache.zeppelin.interpreter.remote.RemoteInterpreter.interpret(RemoteInterpreter.java:190)
>>>>
>>>>         at
>>>> org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:93)
>>>>
>>>>         at
>>>> org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:211)
>>>>
>>>>         at org.apache.zeppelin.scheduler.Job.run(Job.java:169)
>>>>
>>>>         at
>>>> org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:322)
>>>>
>>>>         at
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>>>
>>>>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>
>>>>         at
>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>>>>
>>>>         at
>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>>>>
>>>>         at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>>
>>>>         at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>
>>>>         at java.lang.Thread.run(Thread.java:745)
>>>>
>>>> Caused by: org.apache.zeppelin.interpreter.InterpreterException:
>>>> org.apache.thrift.transport.TTransportException: java.net.ConnectException:
>>>> Connection refused
>>>>
>>>>         at
>>>> org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:53)
>>>>
>>>>         at
>>>> org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:37)
>>>>
>>>>         at
>>>> org.apache.commons.pool2.BasePooledObjectFactory.makeObject(BasePooledObjectFactory.java:60)
>>>>
>>>>         at
>>>> org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:861)
>>>>
>>>>         at
>>>> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
>>>>
>>>>         at
>>>> org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
>>>>
>>>>         at
>>>> org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.getClient(RemoteInterpreterProcess.java:139)
>>>>
>>>>         at
>>>> org.apache.zeppelin.interpreter.remote.RemoteInterpreter.interpret(RemoteInterpreter.java:188)
>>>>
>>>>         ... 11 more
>>>>
>>>>
>>>> Respectfully,
>>>>
>>>> *Kyle Burke *| Data Science Engineer
>>>> *IgnitionOne - *Marketing Technology. Simplified.
>>>> Office: 1545 Peachtree St NE, Suite 500 | Atlanta, GA | 30309
>>>>
>>>
>>>
>>
>

Reply via email to