Like Felix Cheung mentioned, the error could happen when you have multiple
version of jackson-databind in your classpath.
No javascript API for graphs. But having Javascript API is i think really
great idea. Thanks for the suggestion.
Best,
moon
On Wed, Nov 4, 2015 at 1:36 AM Felix Cheung <felixcheun...@hotmail.com>
wrote:
> It is possible there are some version mismatches. As you know, Zeppelin is
> built with a version Spark (and Jackson) - do you know how your copy of
> Zeppelin is built?
>
>
> _____________________________
> From: Ji, Hao Wei Jeffery <jeffery...@dnvgl.com>
> Sent: Tuesday, November 3, 2015 7:38 AM
> Subject: some questions
> To: <users@zeppelin.incubator.apache.org>
>
>
>
> Hi,
>
>
>
> I’m playing with zeppelin for some internal POC. While I had some problem
> running spark shells, I installed zeppelin with ambari, and Hadoop is also
> setup by ambari. The hdp version is 2.3, spark is 1.4.1. while when run
> some spark shell in zeppelin, it returns some Jackson error like below
>
>
>
> val sqlContext = new org.apache.spark.sql.SQLContext(sc)
>
>
>
> val thdFile =
> sc.textFile("hdfs:///user/zeppelin/thddemo/THD_Customer_List_20151003.csv")
>
>
>
> sqlContext: org.apache.spark.sql.SQLContext =
> org.apache.spark.sql.SQLContext@672808bf
>
> com.fasterxml.jackson.databind.JsonMappingException: Could not find
> creator property with name 'id' (in class
> org.apache.spark.rdd.RDDOperationScope)
>
> at [Source: {"id":"0","name":"textFile"}; line: 1, column: 1]
>
>
>
> but these commands are run successfully in the spark-shell CLI, is anyone
> know why?
>
>
>
> And another question for zeppelin dev team, for embedding graphs in html,
> except iframe, is it possible to have javascripts like graphs in tableau?
>
>
>
> Br,
>
> Jeffery
>
>
>
> **************************************************************************************
>
> This e-mail and any attachments thereto may contain confidential
> information and/or information protected by intellectual property rights
> for the exclusive attention of the intended addressees named above. If you
> have received this transmission in error, please immediately notify the
> sender by return e-mail and delete this message and its attachments.
> Unauthorized use, copying or further full or partial distribution of this
> e-mail or its contents is prohibited.
> **************************************************************************************
>
>
>
>
