Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1104
@bzz @astroshim
Took me quite some time to dig into this.
Removing `resultRefreshed` would have negative performances effect, its
original goal is to not re-render things if there was no change. however its
condition isn't that great and a better one would be:
`!angular.equals(data.paragraph.result, $scope.paragraph.result);`
A quick fix is indeed to remove `resultRefreshed`, but from this condition
only `else if (newType === 'TEXT' && resultRefreshed) {`
The overall issue is that the implementation of the streaming feature in
interpreters for the TEXT result type is not consistent.
And since the issue is complex and need of lot of explanations, I will
create a separate issue.
We can keep this PR as a quick fix
---
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.
---
