GitHub user 1ambda reopened a pull request:

    https://github.com/apache/zeppelin/pull/2411

    [ZEPPELIN-2650] fix: DON'T set uppercase automatically for column names in 
table

    ### What is this PR for?
    
    fix: DON'T set uppercase automatically for column names in a table
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    
    DONE
    
    ### What is the Jira issue?
    
    [ZEPPELIN-2650](https://issues.apache.org/jira/browse/ZEPPELIN-2650)
    
    ### How should this be tested?
    
    1. Create a table result
    2. Check the column names
    
    ### Screenshots (if appropriate)
    
    #### Before
    
    
![image](https://user-images.githubusercontent.com/4968473/27167154-51c6fdf2-51da-11e7-990c-ee8c3b8db10b.png)
    
    #### After
    
    
![image](https://user-images.githubusercontent.com/4968473/27167147-44962cd4-51da-11e7-8339-8c14eee305ef.png)
    
    ### Questions:
    * Does the licenses files need update? - NO
    * Is there breaking changes for older versions? - NO
    * Does this needs documentation? - NO


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

    $ git pull https://github.com/1ambda/zeppelin 
ZEPPELIN-2650/do-not-apply-uppercase-for-column-name

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

    https://github.com/apache/zeppelin/pull/2411.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 #2411
    
----
commit b5afb5ae3922c65d7287c92a63fdc74c10eb8ca4
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-15T05:47:26Z

    fix: Set displayName to colDef to use original col name

commit fd1efd3413ca5b4a5cd90913e1effd5748977efb
Author: 1ambda <1am...@gmail.com>
Date:   2017-06-16T03:57:07Z

    fix: SparkIT

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to