Re: Updating the official homepage

[Paul-Armand Verhaegen]

+1 for not starting that war without data on usage.

P

> On 25 May 2017, at 10:56, Partridge, Lucas (GE Aviation) 
>  wrote:
> 
> Some great ideas here.
>  
> I’m just a bit concerned about the most popular interpreters being listed as 
> Spark, JDBC and Python. Is that based on real usage data for the different 
> interpreters; if such data is available?  I’ve never knowingly used the JDBC 
> interpreter, and the team of data scientists I work with mostly use the 
> Python, SQL, Spark and Shell interpreters. But this will probably vary 
> between teams and I don’t want to start a ‘my favourite 3 interpreters’ war!  
> If you’re trying to appeal to the Data Scientist community, assuming that’s 
> the main type of user, we should think of the interpreters that appeal most 
> to them.
>  
> Thanks, Lucas.
>  
> From: Sora Lee [mailto:sora0...@zepl.com ] 
> Sent: 25 May 2017 03:53
> To: users@zeppelin.apache.org 
> Subject: EXT: Re: Updating the official homepage
>  
> +1 Nice design!
>  
> And I also would like to suggest two ideas.
>  
> 1. Adding 'Quick Interpreters Links' to documentations 
> (http://zeppelin.apache.org/ ).
> for example, I attached the following screenshots about Cloudera web site. 
>  
>
>  
>  
> 2. Adding left menu documentation structure such as TensorFlow and Docker web 
> site.
> I think this structure is more comfortable user point of view searching 
> documentation.
> 
> 
>  
> - Docker
>  
> ​
>  
> What do you think of that? 
> If that is okay, I'll make a rough design like Hoon!
> And also any suggestion or advice will be appreciated. 
>  
> Thanks,
> Sora
>  
>  
> 2017-05-25 11:21 GMT+09:00 Park Hoon <1am...@gmail.com 
> >:
> Hi, All! Thanks for replying!
>  
> I created a JIRA ticket for updating official homepage 
> (https://issues.apache.org/jira/browse/ZEPPELIN-2583?jql=project%20%3D%20ZEPPELIN
>  
> )
>  
> Also, I attached a rough design in this email and There are few details and 
> backgrounds for the change.
>  
>  
> 1. Main Page (zeppelin.apache.com ): Header
>  
> ## Before
>  
> 
>  
> ## After
>  
> 
>  
> ## Details
>  
> - Add `Quick Start` menu: which can be helpful for beginner
> - Remove `Github` menu: everyone can search GitHub.com/zeppelin 
>  in google.
> - `Community` menu was moved to before `Apache` menu. That’s because It’s not 
> the most important menu.
>  
>  
>  
> 2. Main Page (zeppelin.apache.com ): Section 1
>  
> ## Before
>  
> 
>  
> ## After
>  
> 
> ## Details 
>  
> The used texts are just coped from somewhere, and design can be improved. So 
> please focus on the structure of the page, not the text.
>  
> - Remove the large `Apache Zeppelin` text. There is no reason to keep it. 
> Everyone knows this is Zeppelin web site. 
> - Replace the outdated `TUTORIAL VIDEO` button to `GET STARTED` button to 
> help new comers.
>  
>  
>  
> 3. Main Page (zeppelin.apache.com ): Section 2
>  
> ## Before
>  
> 
>  
> ## After
>  
> 
>  
> ## Details
>  
> The used texts are just coped from somewhere, and design can be improved. So 
> please focus on the structure of the page, not the text.
>  
> - This is a new section will be located top on (previous) the *new feature* 
> section. 
> - `Spark`, `JDBC` and `Python` are the most important interpreters in 
> Zeppelin and they are what the beginners want to use at first. 
> - depending on the type of users, they have different interests. So  `User / 
> Admin / Contributor` menus will helpful for each group. See the documentation 
> page screenshot for detail.
>  
>  
>  
> 4. Documentation Page (http://zeppelin.apache.org/docs/version/ 
> ): Header
>  
> ## Before
>  
> 
> ## After
>  
> 
>  
> ## Details 
>  
> - Add `User`, `Admin` menus: - menus are now organized based on user types.
> - Remove `Display System` menu. It can be located under `User`
>  
>  
>  
> 5. Documentation Page (http://zeppelin.apache.org/docs/version/ 
> ): Content
>  
> ## Before
>  
> 
>  
> ## After
>  
> 
>  
> ## Details
>  
> - Removed duplicated information which already introduced on the main page. 
> For example spark section, open source section, pivot, built-in 
> visualizations. We have to make user see the documentation which is really 
> important instead of listing features. 
>  
>  
>  
>  
> 6. Documentation Page (http://zeppelin.apache.org/docs/version/ 
> ): Header Details
>  
> ## Before
>  
> 
>  
> ## After
>  
> 
>  
> 
> 
> 
> 
>  
> ## Details
>  
> - The style is changed a little bit for readability.
> - the Interpreter tab shows the most i

Re: Returning more than the default 1000 rows

[Paul-Armand Verhaegen]

I've filed ZEPPELIN-2447 for this bug.
I'll see if I can create PR in github too.

Thanks for the follow-up,
Paul 

> On 22 Apr 2017, at 07:37, moon soo Lee  wrote:
> 
> Thanks for reporting problem and share workaround.
> It looks like PythonInterpreter uses hardcoded value [1] instead of reading 
> max_result from interpreter property.
> Definitely it looks like a bug. Do you mind file an issue to project JIRA [2]?
> 
> Thanks,
> moon
> 
> [1] 
> https://github.com/apache/zeppelin/blob/v0.7.1/python/src/main/resources/python/zeppelin_python.py#L58
>  
> <https://github.com/apache/zeppelin/blob/v0.7.1/python/src/main/resources/python/zeppelin_python.py#L58>
> [2] https://issues.apache.org/jira/browse/ZEPPELIN 
> <https://issues.apache.org/jira/browse/ZEPPELIN>
> 
> On Fri, Apr 21, 2017 at 5:10 AM Paul-Armand Verhaegen 
> mailto:paularmand.verhae...@gmail.com>> 
> wrote:
> 
> running z.__dict in a zeppelin %python paragraph shows that the max_result is 
> not set (the configuration setting is not applied):
> 
> $ z.__dict__ 
> 
> {'javaList': , 
> 'paramOption': , 'z': 
> JavaObject id=t, 'max_result': 2000, '_displayhook':  0x7fe18291baa0>}
> 
> as a workaround, I now issue z.max_result = 2000 to increase the size of the 
> returned csv and that works fine.
> 
> Thanks,
> Paul
> 
>> On 21 Apr 2017, at 13:48, Paul-Armand Verhaegen 
>> mailto:paularmand.verhae...@gmail.com>> 
>> wrote:
>> 
>> 
>> Thanks for your reply. Based on your suggestions I've edited 
>> conf/zeppelin-env.sh adding: 
>> export ZEPPELIN_SPARK_MAXRESULT=1  # Max number of Spark SQL result 
>> to display. 1000 by default.
>> export ZEPPELIN_WEBSOCKET_MAX_TEXT_MESSAGE_SIZE=1024   # Size in 
>> characters of the maximum text message to be received by websocket. Defaults 
>> to 1024000
>> 
>> I've restarted zeppelin, but it still does not show any rows above 1000 
>> (neither visualisation nor csv download).
>> I also doubled checked the settings by adding "env" in the common.sh to 
>> ensure that the settings are properly sourced into the shell, and they are.
>> 
>> Paul
>> 
>>> On 20 Apr 2017, at 23:28, So good <33146...@qq.com 
>>> <mailto:33146...@qq.com>> wrote:
>>> 
>>> The zeppelin configuration file has settings for the maximum number of rows 
>>> and the maximum size of the file.
>>> 
>>> -- 原始邮件 --
>>> 发件人: "Paul-Armand Verhaegen" >> <mailto:paularmand.verhae...@gmail.com>>;
>>> 发送时间: 2017年4月21日(星期五) 3:46
>>> 收件人: "users" mailto:users@zeppelin.apache.org>>;
>>> 主题: Returning more than the default 1000 rows
>>> 
>>> 
>>> Hi,
>>> 
>>> I have problems making zeppelin 0.7.1 (in %python or %spark.pyspark) to 
>>> return more than the default 1000 rows (from a pandas dataframe) in a 
>>> visualisation or csv download.
>>> I tried to increase the values of all maxResults settings in 
>>> interpreter.json, but to no avail (and restarted zeppelin after config 
>>> change).
>>> 
>>> Can someone point me in the right direction?
>>> 
>>> Thanks,
>>> Paul
>> 
> 

Re: Returning more than the default 1000 rows

[Paul-Armand Verhaegen]

running z.__dict in a zeppelin %python paragraph shows that the max_result is 
not set (the configuration setting is not applied):

$ z.__dict__ 

{'javaList': , 
'paramOption': , 'z': 
JavaObject id=t, 'max_result': 2000, '_displayhook': }

as a workaround, I now issue z.max_result = 2000 to increase the size of the 
returned csv and that works fine.

Thanks,
Paul

> On 21 Apr 2017, at 13:48, Paul-Armand Verhaegen 
>  wrote:
> 
> 
> Thanks for your reply. Based on your suggestions I've edited 
> conf/zeppelin-env.sh adding: 
> export ZEPPELIN_SPARK_MAXRESULT=1  # Max number of Spark SQL result 
> to display. 1000 by default.
> export ZEPPELIN_WEBSOCKET_MAX_TEXT_MESSAGE_SIZE=1024   # Size in 
> characters of the maximum text message to be received by websocket. Defaults 
> to 1024000
> 
> I've restarted zeppelin, but it still does not show any rows above 1000 
> (neither visualisation nor csv download).
> I also doubled checked the settings by adding "env" in the common.sh to 
> ensure that the settings are properly sourced into the shell, and they are.
> 
> Paul
> 
>> On 20 Apr 2017, at 23:28, So good <33146...@qq.com <mailto:33146...@qq.com>> 
>> wrote:
>> 
>> The zeppelin configuration file has settings for the maximum number of rows 
>> and the maximum size of the file.
>> 
>> -- 原始邮件 --
>> 发件人: "Paul-Armand Verhaegen" > <mailto:paularmand.verhae...@gmail.com>>;
>> 发送时间: 2017年4月21日(星期五) 3:46
>> 收件人: "users" mailto:users@zeppelin.apache.org>>;
>> 主题: Returning more than the default 1000 rows
>> 
>> 
>> Hi,
>> 
>> I have problems making zeppelin 0.7.1 (in %python or %spark.pyspark) to 
>> return more than the default 1000 rows (from a pandas dataframe) in a 
>> visualisation or csv download.
>> I tried to increase the values of all maxResults settings in 
>> interpreter.json, but to no avail (and restarted zeppelin after config 
>> change).
>> 
>> Can someone point me in the right direction?
>> 
>> Thanks,
>> Paul
> 

Re: Returning more than the default 1000 rows

[Paul-Armand Verhaegen]

Thanks for your reply. Based on your suggestions I've edited 
conf/zeppelin-env.sh adding: 
export ZEPPELIN_SPARK_MAXRESULT=1  # Max number of Spark SQL result to 
display. 1000 by default.
export ZEPPELIN_WEBSOCKET_MAX_TEXT_MESSAGE_SIZE=1024   # Size in 
characters of the maximum text message to be received by websocket. Defaults to 
1024000

I've restarted zeppelin, but it still does not show any rows above 1000 
(neither visualisation nor csv download).
I also doubled checked the settings by adding "env" in the common.sh to ensure 
that the settings are properly sourced into the shell, and they are.

Paul

> On 20 Apr 2017, at 23:28, So good <33146...@qq.com> wrote:
> 
> The zeppelin configuration file has settings for the maximum number of rows 
> and the maximum size of the file.
> 
> ------ 原始邮件 --
> 发件人: "Paul-Armand Verhaegen" ;
> 发送时间: 2017年4月21日(星期五) 3:46
> 收件人: "users" ;
> 主题: Returning more than the default 1000 rows
> 
> 
> Hi,
> 
> I have problems making zeppelin 0.7.1 (in %python or %spark.pyspark) to 
> return more than the default 1000 rows (from a pandas dataframe) in a 
> visualisation or csv download.
> I tried to increase the values of all maxResults settings in 
> interpreter.json, but to no avail (and restarted zeppelin after config 
> change).
> 
> Can someone point me in the right direction?
> 
> Thanks,
> Paul

Returning more than the default 1000 rows

[Paul-Armand Verhaegen]

Hi,

I have problems making zeppelin 0.7.1 (in %python or %spark.pyspark) to return 
more than the default 1000 rows (from a pandas dataframe) in a visualisation or 
csv download.
I tried to increase the values of all maxResults settings in interpreter.json, 
but to no avail (and restarted zeppelin after config change).

Can someone point me in the right direction?

Thanks,
Paul