Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1171
ð
---
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
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1171
I missed this (which solve the same problem as
https://github.com/apache/zeppelin/pull/1182), let me check this.
---
If your project is set up for it, you can reply to this email and
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1171
Thanks @astroshim @corneadoug for review this!
Merge it into master if there're no more discussions.
---
If your project is set up for it, you can reply to this email and have your
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1171
@corneadoug 413 and 473 "together" are alternative fix for ZEPPELIN-1078
for better performance.
Without 413, applying 473 will bring ZEPPELIN-1078 problem again.
---
If your project
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1171
@Leemoonsoo I tested again, originally I was testing with previous `||
resultRefreshed`
473 does help the text rendering indeed. However I have the same
improvement without 413 for both
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1171
@corneadoug I tried more and it looks like slowing down without 413 and 473
change is not consistently reproducible.
Anyway, logically, 413 and 473 change reduce text rendering from
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1171
Build error has gone and working good!
---
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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1171
@Leemoonsoo Tested,
Fix for the table after re-run confirmed.
For the second item, I would keep the solution used in
https://issues.apache.org/jira/browse/ZEPPELIN-1078
Since
