GitHub user liancheng opened a pull request:

    https://github.com/apache/spark/pull/208

    Fixed coding style issues in Spark SQL 

    This PR addresses various coding style issues in Spark SQL, including but 
not limited to those mentioned by @mateiz in PR #146.
    
    As this PR affects lots of source files and may cause potential conflicts, 
it would be better to merge this as soon as possible *after* PR #205 (In-memory 
columnar representation for Spark SQL) is merged.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/liancheng/spark fixCodingStyle

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/208.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #208
    
----
commit 3dcbbbd214587547c8f0d923b393ba4adaac9366
Author: Cheng Lian <[email protected]>
Date:   2014-03-22T11:48:39Z

    Fixed relative package imports for package catalyst

commit 92653664bd67183e4d93c5c166d4cd5ffcf7348a
Author: Cheng Lian <[email protected]>
Date:   2014-03-22T12:17:39Z

    Fixed coding style issues in sql/core

commit fae7b02b43ca86ff4434caf5129bd7353f7f732e
Author: Cheng Lian <[email protected]>
Date:   2014-03-23T08:16:50Z

    Addressed styling issues mentioned by @marmbrus

commit 0b56f77c83a24c46c2e9676523665c18f607acb6
Author: Cheng Lian <[email protected]>
Date:   2014-03-23T08:29:31Z

    Fixed coding style issues in sql/core

commit b531273ee8d9908d0c6f95dce10c4ef02e855fde
Author: Cheng Lian <[email protected]>
Date:   2014-03-23T09:20:57Z

    Fixed coding style issues in sql/hive

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to