CORNEAU Damien created ZEPPELIN-1095:
----------------------------------------
Summary: Inconsistencies in the way TEXT result is sent when
running a paragraph
Key: ZEPPELIN-1095
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1095
Project: Zeppelin
Issue Type: Bug
Reporter: CORNEAU Damien
Fix For: 0.6.1
While reviewing: https://github.com/apache/zeppelin/pull/1104
I ran a few tests, with a proper `resultRefreshed` value:
`!angular.equals(data.paragraph.result, $scope.paragraph.result);`.
I found out that the interpreters do not send back the TEXT type result the
same way, making it difficult to use the resultRefreshed value to not re-render
the same results.
# In Short
* Spark is sending 'PARAGRAPH_UPDATE_OUTPUT' before any
'PARAGRAPH_APPEND_OUTPUT', Fkink and Python (at least) do not.
* Flink and Python (at least) are not sending their data inside a
'PARAGRAPH_APPEND_OUTPUT' event.
* We receive 2 'PARAGRAPH_APPEND_OUTPUT' event with no data, after all the
valid 'PARAGRAPH_APPEND_OUTPUT' were received (even for Flink and Python)
# Possible actions
* Don't use `resultRefreshed` for the TEXT type results.
* Don't use `resultRefreshed` for the TEXT type results, and fix the
inconsistencies.
* Fix the inconsistencies and implement a new PARAGRAPH_ENDSTREAMING_OUTPUT
event
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
