spark git commit: [SPARK-18147][SQL] do not fail for very complex aggregator result type

2016-11-09 Thread wenchen
Repository: spark Updated Branches: refs/heads/branch-2.1 b7d29256b -> 8c489a78d [SPARK-18147][SQL] do not fail for very complex aggregator result type ## What changes were proposed in this pull request? ~In `TypedAggregateExpression.evaluateExpression`, we may create

spark git commit: [SPARK-18147][SQL] do not fail for very complex aggregator result type

2016-11-09 Thread wenchen
Repository: spark Updated Branches: refs/heads/master 3f62e1b5d -> 6021c95a3 [SPARK-18147][SQL] do not fail for very complex aggregator result type ## What changes were proposed in this pull request? ~In `TypedAggregateExpression.evaluateExpression`, we may create `ReferenceToExpressions`

spark git commit: [SPARK-17829][SQL] Stable format for offset log

2016-11-09 Thread zsxwing
Repository: spark Updated Branches: refs/heads/branch-2.1 4424c901e -> b7d29256b [SPARK-17829][SQL] Stable format for offset log ## What changes were proposed in this pull request? Currently we use java serialization for the WAL that stores the offsets contained in each batch. This has two

spark git commit: [SPARK-17829][SQL] Stable format for offset log

2016-11-09 Thread zsxwing
Repository: spark Updated Branches: refs/heads/master 64fbdf1aa -> 3f62e1b5d [SPARK-17829][SQL] Stable format for offset log ## What changes were proposed in this pull request? Currently we use java serialization for the WAL that stores the offsets contained in each batch. This has two main

spark git commit: [SPARK-18191][CORE][FOLLOWUP] Call `setConf` if `OutputFormat` is `Configurable`.

2016-11-09 Thread rxin
Repository: spark Updated Branches: refs/heads/master d8b81f778 -> 64fbdf1aa [SPARK-18191][CORE][FOLLOWUP] Call `setConf` if `OutputFormat` is `Configurable`. ## What changes were proposed in this pull request? We should call `setConf` if `OutputFormat` is `Configurable`, this should be

spark git commit: [SPARK-18370][SQL] Add table information to InsertIntoHadoopFsRelationCommand

2016-11-09 Thread rxin
Repository: spark Updated Branches: refs/heads/branch-2.1 80f58510a -> 4424c901e [SPARK-18370][SQL] Add table information to InsertIntoHadoopFsRelationCommand ## What changes were proposed in this pull request? `InsertIntoHadoopFsRelationCommand` does not keep track if it inserts into a

spark git commit: [SPARK-18370][SQL] Add table information to InsertIntoHadoopFsRelationCommand

2016-11-09 Thread rxin
Repository: spark Updated Branches: refs/heads/master d4028de97 -> d8b81f778 [SPARK-18370][SQL] Add table information to InsertIntoHadoopFsRelationCommand ## What changes were proposed in this pull request? `InsertIntoHadoopFsRelationCommand` does not keep track if it inserts into a table

spark git commit: [SPARK-18368][SQL] Fix regexp replace when serialized

2016-11-09 Thread yhuai
Repository: spark Updated Branches: refs/heads/branch-2.0 c8628e877 -> 6e7310590 [SPARK-18368][SQL] Fix regexp replace when serialized ## What changes were proposed in this pull request? This makes the result value both transient and lazy, so that if the RegExpReplace object is initialized

spark git commit: [SPARK-18368][SQL] Fix regexp replace when serialized

2016-11-09 Thread yhuai
Repository: spark Updated Branches: refs/heads/branch-2.1 626f6d6d4 -> 80f58510a [SPARK-18368][SQL] Fix regexp replace when serialized ## What changes were proposed in this pull request? This makes the result value both transient and lazy, so that if the RegExpReplace object is initialized

spark git commit: [SPARK-18368][SQL] Fix regexp replace when serialized

2016-11-09 Thread yhuai
Repository: spark Updated Branches: refs/heads/master 47636618a -> d4028de97 [SPARK-18368][SQL] Fix regexp replace when serialized ## What changes were proposed in this pull request? This makes the result value both transient and lazy, so that if the RegExpReplace object is initialized then

spark git commit: Revert "[SPARK-18368] Fix regexp_replace with task serialization."

2016-11-09 Thread yhuai
Repository: spark Updated Branches: refs/heads/master 06a13ecca -> 47636618a Revert "[SPARK-18368] Fix regexp_replace with task serialization." This reverts commit b9192bb3ffc319ebee7dbd15c24656795e454749. Project: http://git-wip-us.apache.org/repos/asf/spark/repo Commit:

spark git commit: [SPARK-16808][CORE] History Server main page does not honor APPLICATION_WEB_PROXY_BASE

2016-11-09 Thread vanzin
Repository: spark Updated Branches: refs/heads/branch-2.1 ac441d173 -> 5bd31dc9d [SPARK-16808][CORE] History Server main page does not honor APPLICATION_WEB_PROXY_BASE ## What changes were proposed in this pull request? Application links generated on the history server UI no longer

spark git commit: [SPARK-16808][CORE] History Server main page does not honor APPLICATION_WEB_PROXY_BASE

2016-11-09 Thread vanzin
Repository: spark Updated Branches: refs/heads/master 205e6d586 -> 06a13ecca [SPARK-16808][CORE] History Server main page does not honor APPLICATION_WEB_PROXY_BASE ## What changes were proposed in this pull request? Application links generated on the history server UI no longer (regression

spark git commit: [SPARK-18338][SQL][TEST-MAVEN] Fix test case initialization order under Maven builds

2016-11-09 Thread yhuai
Repository: spark Updated Branches: refs/heads/master 02c5325b8 -> 205e6d586 [SPARK-18338][SQL][TEST-MAVEN] Fix test case initialization order under Maven builds ## What changes were proposed in this pull request? Test case initialization order under Maven and SBT are different. Maven

spark git commit: [SPARK-18292][SQL] LogicalPlanToSQLSuite should not use resource dependent path for golden file generation

2016-11-09 Thread srowen
Repository: spark Updated Branches: refs/heads/branch-2.1 b89c38b2e -> ac441d173 [SPARK-18292][SQL] LogicalPlanToSQLSuite should not use resource dependent path for golden file generation ## What changes were proposed in this pull request? `LogicalPlanToSQLSuite` uses the following command

spark git commit: [SPARK-18292][SQL] LogicalPlanToSQLSuite should not use resource dependent path for golden file generation

2016-11-09 Thread srowen
Repository: spark Updated Branches: refs/heads/master e256392a1 -> 02c5325b8 [SPARK-18292][SQL] LogicalPlanToSQLSuite should not use resource dependent path for golden file generation ## What changes were proposed in this pull request? `LogicalPlanToSQLSuite` uses the following command to

spark git commit: [SPARK-17659][SQL] Partitioned View is Not Supported By SHOW CREATE TABLE

2016-11-09 Thread lixiao
Repository: spark Updated Branches: refs/heads/branch-2.1 f67208369 -> b89c38b2e [SPARK-17659][SQL] Partitioned View is Not Supported By SHOW CREATE TABLE ### What changes were proposed in this pull request? `Partitioned View` is not supported by SPARK SQL. For Hive partitioned view, SHOW

spark git commit: [SPARK-17659][SQL] Partitioned View is Not Supported By SHOW CREATE TABLE

2016-11-09 Thread lixiao
Repository: spark Updated Branches: refs/heads/master b9192bb3f -> e256392a1 [SPARK-17659][SQL] Partitioned View is Not Supported By SHOW CREATE TABLE ### What changes were proposed in this pull request? `Partitioned View` is not supported by SPARK SQL. For Hive partitioned view, SHOW