Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1371
I think that data type discovery should be done on the back-end and sent to
the front.
Parsing every column and rows can become expensive.
And having a good data type discovery structure would also allow APIs to
benefit from it.
While it only applied to table #1363 is more beneficial since it let the
user set the type himself (usually the user knows the type better). We can also
expand it to handle more types, and why not the graph pivot.
---
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.
---
