You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@zeppelin.apache.org by Eyal Hashai <ey...@kenshoo.com> on 2019/09/24 07:23:34 UTC
common.max_result not functional?
Dear Zeppelin user community,
One of our users requested an option to limit the number of rows shown in
Zeppelin UI, while being able to export all the data (with higher
limitation).
We are using a JDBC interpreter that connects to a Hive cluster.
From reading the documentation Zeppelin supports it via these two
parameters:
[image: Screenshot from 2019-09-24 09-56-52.png]
[image: Screenshot from 2019-09-24 09-56-33.png]
* common.max_count* - limits the total number of records
* common.max_result* - limits the results shown in the UI
It also looks like the UI support exporting all data or only visible data
too:
[image: Screenshot from 2019-09-24 10-01-20.png]
common.max_count works well and controls how many rows are returned, but
common.max_result doesn't seem to change anything.
We are using Zeppelin 0.8.0, I did not find any open bug on this issue,
does this feature work? and if not will it work in 0.8.1\2 or 0.9.0 ?
WIll appreciate any leads on this matter, thank you!
*Some technical data:*
*interpreter.json contains this option:*
"common.max_result": {
"name": "common.max_result",
"value": "5",
"type": "number"
},
*Logs show the parameter does pass to the JDBC drive:*
DEBUG [2019-09-23 09:17:25,581] ({pool-2-thread-2}
JDBCInterpreter.java[open]:207) - JDBC PropretiesMap:
{default={url=jdbc:hive2://xxxxxx:10000, completer.schemaFilters=,
user=zeppelin, statementPrecode=, splitQueries=false, password=,
driver=org.apache.hive.jdbc.HiveDriver, completer.ttlInSeconds=120,
precode=}, common={max_result=5, max_count=1000}}
--
Eyal Hashai
<http://www.kenshoo.com/>*Database Administrator - Big Data Team | Kenshoo*
m: +972 (50) 404-0473 *o*: +972 (3) 746-6500 x552
w: www.kenshoo.com l: linkedin.com/eyal-hashai-2667586a
<https://www.linkedin.com/in/eyal-hashai-2667586a/>Named #1 in Search &
Social by Internet Retailer 2015 - 2019
* <Ey...@Kenshoo.com>*
<http://kenshoo.com/>
--
This e-mail, as well as any attached document, may contain material which
is confidential and privileged and may include trademark, copyright and
other intellectual property rights that are proprietary to Kenshoo Ltd,
its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments
may be read, copied and used only by the addressee for the purpose(s) for
which it was disclosed herein. If you have received it in error, please
destroy the message and any attachment, and contact us immediately. If you
are not the intended recipient, be aware that any review, reliance,
disclosure, copying, distribution or use of the contents of this message
without Kenshoo's express permission is strictly prohibited.
Re: common.max_result not functional?
Posted by Jeff Zhang <zj...@gmail.com>.
I think they are for the same purpose, but max_count is used for the 0.8
while max_count is for old version and removed now.
Eyal Hashai <ey...@kenshoo.com> 于2019年9月24日周二 下午3:24写道：
>
> Dear Zeppelin user community,
>
> One of our users requested an option to limit the number of rows shown in
> Zeppelin UI, while being able to export all the data (with higher
> limitation).
> We are using a JDBC interpreter that connects to a Hive cluster.
>
> From reading the documentation Zeppelin supports it via these two
> parameters:
> [image: Screenshot from 2019-09-24 09-56-52.png]
> [image: Screenshot from 2019-09-24 09-56-33.png]
> * common.max_count* - limits the total number of records
> * common.max_result* - limits the results shown in the UI
>
> It also looks like the UI support exporting all data or only visible data
> too:
> [image: Screenshot from 2019-09-24 10-01-20.png]
>
> common.max_count works well and controls how many rows are returned, but
> common.max_result doesn't seem to change anything.
>
> We are using Zeppelin 0.8.0, I did not find any open bug on this issue,
> does this feature work? and if not will it work in 0.8.1\2 or 0.9.0 ?
>
> WIll appreciate any leads on this matter, thank you!
>
>
> *Some technical data:*
>
> *interpreter.json contains this option:*
> "common.max_result": {
> "name": "common.max_result",
> "value": "5",
> "type": "number"
> },
>
> *Logs show the parameter does pass to the JDBC drive:*
> DEBUG [2019-09-23 09:17:25,581] ({pool-2-thread-2}
> JDBCInterpreter.java[open]:207) - JDBC PropretiesMap:
> {default={url=jdbc:hive2://xxxxxx:10000, completer.schemaFilters=,
> user=zeppelin, statementPrecode=, splitQueries=false, password=,
> driver=org.apache.hive.jdbc.HiveDriver, completer.ttlInSeconds=120,
> precode=}, common={max_result=5, max_count=1000}}
>
>
>
> --
>
> Eyal Hashai
> <http://www.kenshoo.com/>*Database Administrator - Big Data Team |
> Kenshoo*
>
> m: +972 (50) 404-0473 *o*: +972 (3) 746-6500 x552
> w: www.kenshoo.com l: linkedin.com/eyal-hashai-2667586a
> <https://www.linkedin.com/in/eyal-hashai-2667586a/>Named #1 in Search &
> Social by Internet Retailer 2015 - 2019
>
>
>
> * <Ey...@Kenshoo.com>*
> <http://kenshoo.com/>
>
> This e-mail, as well as any attached document, may contain material which
> is confidential and privileged and may include trademark, copyright and
> other intellectual property rights that are proprietary to Kenshoo Ltd,
> its subsidiaries or affiliates ("Kenshoo"). This e-mail and its
> attachments may be read, copied and used only by the addressee for the
> purpose(s) for which it was disclosed herein. If you have received it in
> error, please destroy the message and any attachment, and contact us
> immediately. If you are not the intended recipient, be aware that any
> review, reliance, disclosure, copying, distribution or use of the contents
> of this message without Kenshoo's express permission is strictly prohibited.
--
Best Regards
Jeff Zhang