Github user sanjaydasgupta commented on the issue:
https://github.com/apache/zeppelin/pull/3013
Thanks for the input @prabhjyotsingh.
Allow me to list the advantages of both methods, and to suggest a possible
way forward for your consideration.
1) **The legacy method has two big advantages**:
a) It is well known, so making it disappear without notice will be a very
unpleasant jolt to all existing users.
b) Being always available, it is usable when either the grid or any
visualization is displayed.
2) **The ui-grid menu approach has the following advantages**:
a) It does not suffer from the problems mentioned in the
[issue](https://issues.apache.org/jira/browse/ZEPPELIN-3511) - though one of
them has been fixed.
b) It allows downloading to an Excel file as well.
c) Being based on a 3rd party package, the support effort will be less, and
periodic enhancements can be expected automatically.
Considering everything, it would seem that the advantage in 1(a) will be
the main loss. The loss of 1(b) will become acceptable once users are familiar
with the new method, as users can switch to the grid to download data.
If we agree to move progressively towards the ui-grid menu approach
(without confusing users who are familiar with the legacy method) the following
could be an option:
In place of the legacy method button and dropdown we add a label with a
tool-tip popup that informs the user where the data-download method has moved.
This informative label can be maintained for one or two releases, by when all
users will be familiar with the new menu. The label can then be removed.
---
