Github user herval commented on the issue:

    https://github.com/apache/zeppelin/pull/2428
  
    I am using the original setting (getMaxResults). I had to set it in two 
calls because setFetchSize will determine that there is a “next” page, but 
if I only do “setMaxResults”, it will not display the truncation warning 
(as it translates to a “limit”)
    
    ________________________________
    From: Felix Cheung <notificati...@github.com>
    Sent: Thursday, June 29, 2017 9:30:44 PM
    To: apache/zeppelin
    Cc: Herval Freire; Mention
    Subject: Re: [apache/zeppelin] [ZEPPELIN-1470] limiting results from jdbc 
(#2428)
    
    
    got it. I agree it's generally better to restrict the job at the source
    perhaps you can use the existing settings but apply it at the JDBC instead? 
it would be easier to switch existing user over the new behavior this way - 
actually, let's see what other thinks about this approach.
    
    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on 
GitHub<https://github.com/apache/zeppelin/pull/2428#issuecomment-312172202>, or 
mute the 
thread<https://github.com/notifications/unsubscribe-auth/AAAV6lwqItW73HbpQPIjLnKd6M4nnvryks5sJHn0gaJpZM4OBqFf>.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to