Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/3360#issuecomment-63720314
I think just referencing the property by its full name and allowing the
user to look it up should be sufficient. Recommending boosting the limit is not
right in all situations - e.g. in some situations the user might be thinking an
action was a transformation and didn't mean to pull all the data to the driver.
@andrewor14 the current documentation references 0 as unlimited so we
should change that too if we switch to -1.
> On Nov 19, 2014, at 12:30 PM, andrewor14 <[email protected]> wrote:
>
> Hey @nishkamravi2 the changes here look good. Just so I understand, the
purpose of treating 0 as unlimited is to provide a way for user to raise the
limit when they hit it, correct? I would even go further to tell the user to
set it to -1; to me it's clearer that maxResultSize can't be negative and so it
must be some magic number.
>
> â
> Reply to this email directly or view it on GitHub.
>
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
