Github user lw-lin commented on the issue:
https://github.com/apache/spark/pull/14370
@rxin @cloud-fan sorry for the ambiguity, but we're not enforcing this.
There are 3 levels:
- when `NO_OP` is on (which is the fault), we do nothing at all to a huge
method;
- when `WARN_...` is on, we'll just log a warning;
- when `ERROR...` is on, we fail fast.
So by default, this does not affect anything on end-user's side. We should
turn on `ERROR_IF_EXCEEDS_JIT_LIMIT` **_only in test suits_** and only against
critical methods, so that we can find performance issues asap because it fails
fast.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
