GitHub user Peilin-Yang reopened a pull request:

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

    [ZEPPELIN-1371]add text/numeric conversion support to table display

    ### What is this PR for?
    We people in Twitter have great demand of adding a flexible drop down menu 
for the columns in the tables which enables the text/numeric conversion.
    This is because people want some columns to be of string type which, for 
example, fits to the underlying DB definition.
    The use cases of the change include:
    
    1. For now sorting on the columns is always lexicographically because 
Zeppelin front end treats the data as strings. It the values in the table can 
be convertible between string and number then we can sort the column by numeric 
values. I have filed another ticket for this: 
https://issues.apache.org/jira/browse/ZEPPELIN-1372
    2. Since the users know more about their data than us it would be nice if 
we let the users decide what is the real type of their data. It is annoying if 
user wants the column to be strings but the front end forcefully inserts commas 
in it. In some scenarios, users may also want to copy/paste the table to 
somewhere else. If people want to remove the commas before other actions then 
that will be a nightmare.... 
    
    
    ### What type of PR is it?
    [Improvement | Feature]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1371
    
    ### How should this be tested?
    
    1. Click on the dropdown menu would convert the text/number of that column.
    2. Other functionalities esp. the sorting function should not be affected.
    
    ### Screenshots (if appropriate)
    
![image](https://cloud.githubusercontent.com/assets/3334391/18445617/76071f8e-78ec-11e6-93a6-fdcf7b85b6e9.png)
    
![image](https://cloud.githubusercontent.com/assets/3334391/18446601/16cff4f0-78f1-11e6-9fd6-4010b5d77f17.png)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? Probably a noticeable 
change in UI
    * Does this needs documentation? No
    


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

    $ git pull https://github.com/Peilin-Yang/zeppelin 
ypeilin/table_num_cell_format

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

    https://github.com/apache/zeppelin/pull/1500.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 #1500
    
----
commit e1ebfd34285a1ff68a345bedb83f830600dd62a5
Author: Peilin Yang <yangpei...@gmail.com>
Date:   2016-10-10T16:35:04Z

    add dropdown menu applied on the latest branch

commit 7eb4f58d69a1dbc78191a981166508e464018d47
Author: Peilin Yang <yangpei...@gmail.com>
Date:   2016-10-13T10:30:42Z

    update the test case in SparkParagraphIT

commit 2caf46e307eb6665aaddd3ef22c6e9aadaf7090e
Author: Peilin Yang <yangpei...@gmail.com>
Date:   2016-10-16T13:15:24Z

    update the test case

commit 902fd900b141f4888f1a0c37db16ed5b2fba7890
Author: Peilin Yang <yangpei...@gmail.com>
Date:   2016-10-18T13:53:21Z

    update test case

----


---
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