spark git commit: [SPARK-13157] [SQL] Support any kind of input for SQL commands.

Repository: spark Updated Branches: refs/heads/master c4feec26e -> 9dd2741eb [SPARK-13157] [SQL] Support any kind of input for SQL commands. The ```SparkSqlLexer``` currently swallows characters which have not been defined in the grammar. This causes problems with SQL commands, such as:

spark git commit: [SPARK-13079][SQL] Extend and implement InMemoryCatalog

Repository: spark Updated Branches: refs/heads/master a8e2ba776 -> a64831124 [SPARK-13079][SQL] Extend and implement InMemoryCatalog This is a step towards consolidating `SQLContext` and `HiveContext`. This patch extends the existing Catalog API added in #10982 to include methods for

spark git commit: [SPARK-13152][CORE] Fix task metrics deprecation warning

Repository: spark Updated Branches: refs/heads/master de0914522 -> a8e2ba776 [SPARK-13152][CORE] Fix task metrics deprecation warning Make an internal non-deprecated version of incBytesRead and incRecordsRead so we don't have unecessary deprecation warnings in our build. Right now

spark git commit: [SPARK-3611][WEB UI] Show number of cores for each executor in application web UI

Repository: spark Updated Branches: refs/heads/master 9dd2741eb -> 3221eddb8 [SPARK-3611][WEB UI] Show number of cores for each executor in application web UI Added a Cores column in the Executors UI Author: Alex Bozarth Closes #11039 from ajbozarth/spark3611.

spark git commit: [SPARK-13113] [CORE] Remove unnecessary bit operation when decoding page number

Repository: spark Updated Branches: refs/heads/master c2c956bcd -> d39087147 [SPARK-13113] [CORE] Remove unnecessary bit operation when decoding page number JIRA: https://issues.apache.org/jira/browse/SPARK-13113 As we shift bits right, looks like the bitwise AND operation is unnecessary.

spark git commit: [SPARK-12828][SQL] add natural join support

Repository: spark Updated Branches: refs/heads/master a64831124 -> 0f81318ae [SPARK-12828][SQL] add natural join support Jira: https://issues.apache.org/jira/browse/SPARK-12828 Author: Daoyuan Wang Closes #10762 from adrian-wang/naturaljoin. Project:

spark git commit: [ML][DOC] fix wrong api link in ml onevsrest

Repository: spark Updated Branches: refs/heads/branch-1.6 cdfb2a141 -> 2f390d306 [ML][DOC] fix wrong api link in ml onevsrest minor fix for api link in ml onevsrest Author: Yuhao Yang Closes #11068 from hhbyyh/onevsrestDoc. (cherry picked from commit

spark git commit: [ML][DOC] fix wrong api link in ml onevsrest

Repository: spark Updated Branches: refs/heads/master 0f81318ae -> c2c956bcd [ML][DOC] fix wrong api link in ml onevsrest minor fix for api link in ml onevsrest Author: Yuhao Yang Closes #11068 from hhbyyh/onevsrestDoc. Project:

spark git commit: [SPARK-12828][SQL] Natural join follow-up

Repository: spark Updated Branches: refs/heads/master d39087147 -> dee801adb [SPARK-12828][SQL] Natural join follow-up This is a small addendum to #10762 to make the code more robust again future changes. Author: Reynold Xin Closes #11070 from

spark git commit: [SPARK-12739][STREAMING] Details of batch in Streaming tab uses two Duration columns

Repository: spark Updated Branches: refs/heads/master 138c300f9 -> e9eb248ed [SPARK-12739][STREAMING] Details of batch in Streaming tab uses two Duration columns I have clearly prefix the two 'Duration' columns in 'Details of Batch' Streaming tab as 'Output Op Duration' and 'Job Duration'

spark git commit: [SPARK-12739][STREAMING] Details of batch in Streaming tab uses two Duration columns

Repository: spark Updated Branches: refs/heads/branch-1.6 2f8abb4af -> 5fe8796c2 [SPARK-12739][STREAMING] Details of batch in Streaming tab uses two Duration columns I have clearly prefix the two 'Duration' columns in 'Details of Batch' Streaming tab as 'Output Op Duration' and 'Job

spark git commit: [SPARK-12798] [SQL] generated BroadcastHashJoin

Repository: spark Updated Branches: refs/heads/master e9eb248ed -> c4feec26e [SPARK-12798] [SQL] generated BroadcastHashJoin A row from stream side could match multiple rows on build side, the loop for these matched rows should not be interrupted when emitting a row, so we buffer the output