An example service
definition under /etc/systemd/system/foo.service
:
[Unit]
Description=Foo Service
After=network.target
[Service]
An example service
definition under /etc/systemd/system/foo.service
:
[Unit]
Description=Foo Service
After=network.target
[Service]
import java.io.DataInputStream; | |
import java.io.EOFException; | |
import java.io.IOException; | |
import org.apache.commons.io.IOUtils; | |
import org.apache.commons.io.input.BoundedInputStream; | |
import org.apache.hadoop.conf.Configuration; | |
import org.apache.hadoop.fs.ContentSummary; | |
import org.apache.hadoop.fs.FSDataInputStream; | |
import org.apache.hadoop.fs.FSDataOutputStream; |
import java.io.File; | |
import java.io.IOException; | |
import org.apache.logging.log4j.LogManager; | |
import org.apache.logging.log4j.Logger; | |
import org.apache.spark.launcher.SparkAppHandle; | |
import org.apache.spark.launcher.SparkLauncher; | |
/** | |
* An example of submitting a Spark application in a programmatic manner | |
*/ |
See https://livy.apache.org/docs/latest/rest-api.html
Let app.json
be the JSON payload that represents the application:
{
"file": "hdfs:///user/user/apps/hello-spark-0.0.1.jar",
"className": "acme.hello_spark.Grep",
"args": ["input/1.txt", "[Mm]agic"],
To list properties of a directory we must use the PROPFIND
method of WebDAV protocol and provide a request body with properties we are interested into.
We must also provide the Depth
header (otherwise the request is rejected as 403 Forbidden
).
To retrieve basic properties as size and type, prepare a request body (say propfind-basic.xml
) as:
We need to enable at least the following modules: headers
, env
, proxy
, proxy_http
, proxy_balancer
.
If we are proxying over AJP of course we should also enable proxy_ajp
.
The following is a sample configuration for a site acting as a balancer to 2 instances of a backend application:
<IfModule mod_ssl.c>
<VirtualHost 192.168.1.6:443>
#include <iostream> | |
using namespace std; | |
constexpr int get_magic_number(int x) | |
{ | |
return x + 1999; | |
} | |
template <int N> |
A resource file can be archived without breaking the file hierarchy that CKAN builds under /var/lib/files/resources
. The actual data for a resource 7896ea0c-504d-401c-818f-065430419695 will be stored as a regular file under a 3-level hierarchy at 789/6ea/0c-504d-401c-818f-065430419695
.
For example:
tree resources
...