Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/3239
@monsieurp I though about it again, and feel that providing 2 properties is
very confusing to users. I think it is better to give one property
(zeppelin.jdbc.maxRows) what is user care about. `zeppelin.jdbc.rowsFetchSize`
is internal property that zeppelin should configure to users. Here's one post
explain the difference between `setFetchSize` and `setMaxRows`
https://stackoverflow.com/questions/32399546/what-is-the-difference-between-statement-setmaxrows-vs-statement-setfetchsize-in?lq=1
---
