Hey guys,
I am trying to get zeppelin to work with my HDP cluster with spark,
cassandra, and yarn. Unfortunately, for the last three days I have
been trying multiple compilation options, configuration settings,
adjusting pom.xml, etc. I just cannot seem to get it working. Have any
of you been able
There might be some usefull information in the thread Guava 16.0
Cassandra Error
using Zeppelin 0.60/Spark 1.6.1/Cassandra 3.4
On Tue, Apr 19, 2016 at 4:12 PM, George Webster wrote:
> Hey guys,
>
> I am trying to get zeppelin to work with my HDP cluster with spark,
> cassandra, and yarn. Unfortu
Hi,
I am trying to use the filters aggregation of elastic search
https://www.elastic.co/guide/en/elasticsearch/reference/2.2/search-aggregations-bucket-filters-aggregation.html
As documented on the elastic page, I made the following query through
zeppelin
{
"aggs" : {
"messages" : {
Yeah it does look like the guava issue.
That thread is what what has me currently adding
com.datastax.spark:spark-cassandra-connector_2.10:1.6.0-M2 and
com.google.guava:guava:16.0.1 to Dependencies in the interpreter
configuration under spark. No dice though. still throw the error
On Tue, Apr 19,
Hello,
You are right, there are some limitations with the Elasticsearch
interpreter.
I have developed it and I'am going to check how I can change the component
to take into account this kind of more complex request.
Regards,
Bruno
2016-04-19 18:53 GMT+02:00 ashish rawat :
> Hi,
>
> I am trying
Thanks Bruno for the prompt reply. Do you know of any indirect way of
achieving the same, i.e. timeseries' of all values of a field (eg logLevel,
httpMethod)
Regards,
Ashish
On Tue, Apr 19, 2016 at 10:38 PM, Bruno Bonnin wrote:
> Hello,
>
> You are right, there are some limitations with the Ela
Hi Bruno,
I am encountering another issue, which might also be related to the
interpreter.
When using the "fields" attribute in the query to select the exact fields
to return, I get an "Error: String is null" through Zeppelin, while the
same query works through the REST interface.
I noticed that
Hi Bruno,
I believe I have found the issue. There indeed is a dependency on the
_source fields in this line 461
final String json = hit.getSourceAsString();
Regards,
Ashish
On Wed, Apr 20, 2016 at 12:05 AM, ashish rawat wrote:
> Hi Bruno,
>
> I am encountering another issue, which might also
Hi All,
Today I found out a bug when review Zeppelin's code: when table's result is
bigger, sometimes the result can't show them all. Let's see code here
Paragraph.controller.js, line 1116
1. We first set graph.height as _graph.height
2. Then in SetTable we set table's height is par
Hi Dafeng,
Can you provide a small query example?
Normally the Table has a scrollbar.
On Wed, Apr 20, 2016 at 12:17 PM, Dafeng Wang wrote:
> Hi All,
>
>
>
> Today I found out a bug when review Zeppelin’s code: when table’s result
> is bigger, sometimes the result can’t show them all. Let’s see
An example will be:
1. Let’s say you have hive connected behind and have databases name great
than 9
2. Then run %sql show databases
3. You probably will hit this issue
Regards,
Dafeng
From: Corneau Damien [mailto:cornead...@gmail.com]
Sent: Tuesday, April 19, 2016 10:37 PM
Typo, sorry, fix it as below
è Have the number of databases greater than 9, not name.
Regards,
Dafeng
From: Dafeng Wang
Sent: Wednesday, April 20, 2016 1:02 AM
To: users@zeppelin.incubator.apache.org
Subject: RE: Bugs in Interpreter result display for table when result's length
is a little big
12 matches
Mail list logo
