Skip to content

Conversation

@rxin
Copy link
Contributor

@rxin rxin commented Mar 14, 2017

What changes were proposed in this pull request?

This patch moves SQLConf from sql/core to sql/catalyst. To minimize the changes, the patch used type alias to still keep CatalystConf (as a type alias) and SimpleCatalystConf (as a concrete class that extends SQLConf).

Motivation for the change is that it is pretty weird to have SQLConf only in sql/core and then we have to duplicate config options that impact optimizer/analyzer in sql/catalyst using CatalystConf.

How was this patch tested?

N/A

@SparkQA
Copy link

SparkQA commented Mar 14, 2017

Test build #74484 has finished for PR 17285 at commit bbf0211.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Mar 14, 2017

Test build #74485 has finished for PR 17285 at commit c199469.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
  • class SQLConf extends Serializable with Logging

* for ticket SPARK-19944 (moves SQLConf from sql/core to sql/catalyst). This class should
* eventually be removed (test cases should just create SQLConf and set values appropriately).
*/
case class SimpleCatalystConf(
Copy link
Contributor

@hvanhovell hvanhovell Mar 14, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does SQLConf contain these defaults?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it does.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is just to keep the code change minimal.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I figured as much.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup the purpose is to minimize the change. Otherwise I will change 50+ files ...

.internal()
.stringConf
.createWithDefault(classOf[ParquetOutputCommitter].getName)
.createWithDefault("org.apache.parquet.hadoop.ParquetOutputCommitter")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a bit weird to me that we refer to sql/core configs in catalyst. Shouldn't we just move the dynamic configuration and the catalyst only configurations to CatalystConf and make SQLConf extend this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea good idea

@cloud-fan
Copy link
Contributor

LGTM, merging to master.

We should have a follow-up PR to further clean up the code and address some comments.

@asfgit asfgit closed this in 0ee38a3 Mar 14, 2017
@gatorsmile
Copy link
Member

A late LGTM

rxin added a commit to rxin/spark that referenced this pull request Mar 15, 2017
This patch moves SQLConf from sql/core to sql/catalyst. To minimize the changes, the patch used type alias to still keep CatalystConf (as a type alias) and SimpleCatalystConf (as a concrete class that extends SQLConf).

Motivation for the change is that it is pretty weird to have SQLConf only in sql/core and then we have to duplicate config options that impact optimizer/analyzer in sql/catalyst using CatalystConf.

N/A

Author: Reynold Xin <[email protected]>

Closes apache#17285 from rxin/SPARK-19944.
ghost pushed a commit to dbtsai/spark that referenced this pull request Apr 4, 2017
## What changes were proposed in this pull request?

This is a follow-up of apache#17285 .

## How was this patch tested?

existing tests

Author: Wenchen Fan <[email protected]>

Closes apache#17521 from cloud-fan/conf.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants