diff options
| author | zsxwing <zsxwing@gmail.com> | 2015-09-19 18:22:43 -0700 |
|---|---|---|
| committer | Yin Huai <yhuai@databricks.com> | 2015-09-19 18:22:43 -0700 |
| commit | e789000b88a6bd840f821c53f42c08b97dc02496 (patch) | |
| tree | 454cf87addc9fe93e9eab98744ce5daa4dcfb6e3 /docs/configuration.md | |
| parent | d83b6aae8b4357c56779cc98804eb350ab8af62d (diff) | |
| download | spark-e789000b88a6bd840f821c53f42c08b97dc02496.tar.gz spark-e789000b88a6bd840f821c53f42c08b97dc02496.tar.bz2 spark-e789000b88a6bd840f821c53f42c08b97dc02496.zip | |
[SPARK-10155] [SQL] Change SqlParser to object to avoid memory leak
Since `scala.util.parsing.combinator.Parsers` is thread-safe since Scala 2.10 (See [SI-4929](https://issues.scala-lang.org/browse/SI-4929)), we can change SqlParser to object to avoid memory leak.
I didn't change other subclasses of `scala.util.parsing.combinator.Parsers` because there is only one instance in one SQLContext, which should not be an issue.
Author: zsxwing <zsxwing@gmail.com>
Closes #8357 from zsxwing/sql-memory-leak.
Diffstat (limited to 'docs/configuration.md')
0 files changed, 0 insertions, 0 deletions