I set property zeppelin.notebook.cron.enable to true in
$ZEPPELIN_HOME/conf/zeppelin-site.xml to enable Cron feature.
I don't see the scheduler button. I'm using the docker image with tag 0.8.2
I checked both old and new notebooks
I've experienced the same and manage to fix by doing / considering the ff:
Make sure that the zeppelin.notebook.cron.enable property is not inside a comment block
<!-- GitHub configurations ...<property>...</property>... -->
Value of zeppelin.notebook.cron.folders must be "/"
Hope this helps. Cheers!
Related
I am building a a demo/training environment for one of our products which work with Hive & Spark. I am using HDP 2.6.5 and If I configure the hive settings I need (primarily these: ACID Settings) through the Ambari GUI it works fine. But I want to automate this and setting these in hive-site.xml is not working (I have found many copies of this file, so it could simply be I am using the wrong one? )
How can I change from the command line what changes when I make changes in Dashboard->Hive->Configs ?
Where are these changes stored? I am sure I have missed something obvious in the docs, but I can't find it.
Thanks!
#Leigh K You should check out the Ambari REST API to make changes to hive. I did not find a quick link to official documentation, but I was able to find this post that goes into detail using PIG:
https://markobigdata.com/2018/07/22/adding-service-to-hdp-using-rest-api/2/
I want to script my Jenkins installation. I use always use the "stable" release of Jenkins (currently : 2.121.3), but I noticed that when I install the stable release, the update website (in admin > plugin > advance) is setted to "https://updates.jenkins.io/update-center.json" which is not the stable release. I have to change this setting to "http://updates.jenkins-ci.org/stable/update-center.json".
I want to do it automatically, by script. I know I can change this setting in the /var/lib/jenkins/hudson.model.UpdateCenter.xml file, but I prefere to use a Groovy script to do this.
But I cant find a way to change this settings in Groovy scriptbecause i'm not aware of the Jenkins/Hudson data model neither the Groovy syntax, I dont know how to change and save the setting.
I was also searching for something like this, I just solved this using groovy, hope this helps anyone else as well.
import hudson.model.UpdateCenter;
import hudson.model.UpdateSite;
import hudson.util.PersistedList;
import jenkins.model.Jenkins
site = "http://updates.jenkins.io/update-center.json"; // TBD: update as necessary
PersistedList < UpdateSite > sites = Jenkins.getInstance().getUpdateCenter().getSites();
for (UpdateSite s: sites) {
if (s.getId().equals(UpdateCenter.ID_DEFAULT))
sites.remove(s);
}
sites.add(new UpdateSite(UpdateCenter.ID_DEFAULT, site));
As for the current Jenkins core API version (>2.16X),
The UpdateCenter Javadoc and UpdateSite Javadoc do not display any method that allows to either add or update the update site.
The UpdateCenter Class source code confirms that the values of the update sites are actually loaded (I suppose at the start of Jenkins) with no possibility to alter the lists afterwards.
So I guess the only way to set a custom update site is to have a custom update site is to feed Jenkins with a custom hudson.model.UpdateCenter.xml at the start.
Here're a couple of observations that I made (please confirm or invalidate in the comments below, as I'm not 100% sure about these):
the custom update site must have id default
discovery of plugins seems to fail at first start. Jenkins must be re-started in order to discover plugins.
I am using liferay 6.1.0 GA1.
In my project, I am using two nodes for my portal.
When I'm using default liferay shutdown option, it's restarting one, which I suppose is good behaviour. Is there any way I can synergize/merge this liferay shutdown option to work on both nodes?
Edit: Additional question. Where I can change default behaviour of shutdown?
I have not done something like this. But here in docs i gives some ideas.
global.shutdown.events=com.liferay.portal.events.GlobalShutdownAction
When you define this action in portal-ext.properties and implement it, it will run when the portal shuts down. In this action you can call a custom script to stop the other instances also.
Following is my addition to portal-ext.properties for setting up ImageMagick with Liferay
I have installed ImageMagick in D drive as mention below :
imagemagick.global.search.path=D:\\ImageMagick-6.8.3-Q16
imagemagick.enabled=true
preview functionality:
dl.file.entry.preview.enabled=true
dl.file.entry.thumbnail.enabled=true
Set this to true to enable conversion and previewing of videos in the Document Library portlet:
xuggler.enabled=true
In Server Administration--->External servics tab, I have configured it correctly and also downloaded/install jar related to Xuggler.
However, above settings are not working for me to generate preview functionality.
I am not even getting message dispalyed like "Generating preview require few more time, please refresh the page after some time....blah blah blah...."
Any help is appreciated.
Thanks.
Have you configured Xuggler properly? Do you get an UnsatisfiedLinkError exception?
See Xuggler's FAQ for the steps to configure your path properly
If it shows that message "Generating preview...", seems that Liferay doesn't detect this file as a video file (the Mime Type isn't any of the values in the property: dl.file.entry.preview.video.mime.types).
I also saw this problem when uploading videos using some browsers. Try uploading using another one.
For me, the solution was to symlink /usr/bin/convert to /usr/local/bin/convert
Whatever I did, nothing seemed to work. All configuration was pointing to /usr/bin (both control panel and portal-ext.properties). As a last resort, not really believing that it will work, I just did the symlink, as that was the default location for liferay.
And it works! All my configuration still points to /usr/bin. So... it looks like liferay just ignores all that config and only looks to default folder.
I'm using Ubuntu 12.04, imagemagick from package manager. Liferay 6.1.2 GA3.
I hope it helps someone.
I have created a feature and i am auto activating it whenever 'My Site' gets created.
I am activating it for the template SPSMSITEHOST.
This feature changes the Picture URL property of User Profile.
Now, the problem is my feature gets activated but it seems it does not execute the code by default and and does not change the picture URL property.
When i deactivate the feature and activate the feature again then feature works absolutely fine as expected.
P.S: I am facing this issue on Production server, surprisingly this work fine on Staging server , i mean the same code !!
Any help ??
Thanks.
Sounds like something becomes out of sync on your production environment. Could it be caused by load balancing?
Are you doing this through STSADM commands?
I would stick the following line after after each command:
stsadm -o execadmsvcjobs
This will make sure processing for previous commands is done before moving on.
If thats way off then I would think its something to do with:
a) The way you're activating the feature... if you're using feature stapling, are you sure that the latest version of your stapling mechanism is in place?!
b) Assuming you have some sort of feature receiver in your code behind. Are you sure there isn't an error occurring thats being hidden by a try catch? If there is then you need to see what the exception is...
If it works when you deactivate/activate the feature, that almost eliminates security issues.
Hope this helps..
After long investigating and search for this problem i tried to rearrange the features at package file depending on the features dependencies, it seems SharePoint activate these features one by one as it's arranged in the package file and this is worked for me :)