Replacing the service definition files alone isn't quite enough. You have to do the following to make sure that the server picks up the new service defs and redeploys the topology hosting the affected service:
1. change rewrite rules 2. restart gateway so that the gateway is aware of the new service def 3. touch/save the topology hosting the ZEPPELIN services so that they redeploy On Fri, Aug 31, 2018 at 7:04 PM Lian Jiang <jiangok2...@gmail.com> wrote: > Thanks Sandeep. Could you please clarify the patching process? > > There is existing rewrite.xml and service.xml under > /var/lib/knox/data-3.0.0.0-1634/services/zeppelinui/0.6.0 on the knox host. > None of below makes zeppelin sql interpreter work: > > 1. Put the new rewrite.xml and service.xml into new created 0.8.0 folder > and restart knox > 2. Replace these two files under 0.6.0 with the two new files and restart > knox > > Appreciate any clue. > > On Fri, Aug 31, 2018 at 1:15 PM Sandeep Moré <moresand...@gmail.com> > wrote: > >> Knox master has patch for this issue >> https://issues.apache.org/jira/browse/KNOX-1424 >> >> You can try applying the patch it should fix the issue. >> >> Best, >> Sandeep >> >> On Fri, Aug 31, 2018 at 12:18 PM Lian Jiang <jiangok2...@gmail.com> >> wrote: >> >>> I am using HDP3.0 (having zeppelin 0.8.0). >>> >>> Below queries do not show any result, even though downloading the csv >>> show the data correctly (e.g. if there is no tables, show the header). >>> >>> %livy2.sql >>> show tables >>> >>> %spark2.sql >>> show tables >>> >>> Infrequently I saw the table show a short time and then disappear. I >>> guess it is html rendering issue. >>> >>> This issue does not happen when I ssh to the zeppelin host and use >>> zeppelin via port forwarding. It happens when I use zeppelin via knox. >>> >>> Any idea? Any setting is related to this? Sql interpreters worked fine >>> in HDP2.6 using zeppelin 0.7.3. >>> >>> >>> javascript error: >>> Error: [ngRepeat:iidexp] '_item_' in '_item_ in _collection_' should be >>> an identifier or '(_key_, _value_)' expression, but got >>> '/gateway/ui/zeppelin/app'. >>> >>> http://errors.angularjs.org/1.5.7/ngRepeat/iidexp?p0=%2Fgateway%2Fui%2Fzeppelin%2Fapp >>> b/<@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:376 >>> Kg</<.compile@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:40:30580 >>> Z@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:37:4755 >>> S@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:30480 >>> S@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:30611 >>> S@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:30611 >>> N@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:29413 >>> X/<@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:37:440 >>> d@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:30833 >>> m@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:37:909 >>> mg</<.link/<@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:40:17582 >>> xc/this.$get</o.prototype.$digest@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:38:10966 >>> a/n.prototype.safeDigest@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:76:1460 >>> b@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:76:3748 >>> a/n.prototype._onMessageHandler@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:76:3960 >>> R/<@ >>> https://mydomain.com/gateway/ui/zeppelin/scripts/vendor.49d751b0c72342f6.js:36:5633 >>> " <!-- ngRepeat: /gateway/ui/zeppelin/app in apps --> >>> >>> >>> >>> Appreciate any clue. >>> >>
