Current snapshot:

MongoDB

You'll need a database as the central node for Hydra. Currently, the only supported database is MongoDB. Simply install and start MongoDB.

You have two alternatives, either build Hydra yourself to get the very latest features, or download the latest released (and stable).

You can find the latest released build on the download page. The file you are looking for is the one named hydra-core-{latest_version}.jar.

If you want to get involved in development of the framework, or simply want to try out the latest new features, you will need to build it yourself. Building Hydra, however, is very simple.

There are a few pre-requisites: Hydra is built with Maven, and as such you will need to install and set up maven. You will also need to have a MongoDB instance running for some of the tests to pass.

1. Clone the repository.
2. In the root directory, run mvn clean install
3. To start, run java -jar hydra-core.jar from inside the bin directory

Once you have a running pipeline system, you can now start adding some some stages to it. For the most basic pipeline, you'll want to load at least two stage libraries into Hydra: basic-stages and solr-out (if you are connecting Hydra to send documents to Solr).

You'll find the projects to build these two (using Maven) in stages/processing/basic and stages/output/solr.

You can either script your pipeline setup with the database-impl/mongo package, or you can use the CmdlineInserter-class that you can find in the examples project under the Hydra root. If you run mvn clean install on that project, you will get a runnable jar that you can use (java -jar inserter-jar-with-dependencies.jar) Below, we'll assume that's the method you are using.

When inserting the library, you will need to provide the name of the jar and an ID that uniquely identifies this library. Should you give an ID that already exists, the old library will be overwritten and any pipeline stages being run from it will be restarted.

Run the CmdlineInserter class (or the jar) with the following arguments: -a -p pipeline -l -i {my-library-id} {my-jar-with-dependencies.jar}

Now that you have a library inserted, you can add your stage by referencing the library id.

In order to configure a stage, you'll need to know what stage it is you want to configure. A configuration for a SetStaticField-stage might look like this:

{
	stageClass: "com.findwise.hydra.stage.SetStaticFieldStage",
	query: {"touched" : {"extractTitles" : true}, "exists" : {"source" : true} },
	fieldNames: ["source"],
	fieldValues: ["web"]
}

• stageClass: Required. Must be the full name of the stage class to be configured.
• query: A serialized version of the query, that all documents this stage receives must match. In this example, all documents received by this stage will have already been processed by a stage called extractTitles and they all have a field called source.
• fieldNames/fieldValues: The input parameters specific for this stage. In this case, it expects two lists.

Save the configuration in a file somewhere on disk, e.g. {mystage.properties}, for ease of use.

Run the CmdlineInserter class (or the jar) with the following arguments: -a -p pipeline -s -i {my-library-id} -n {my-stage-name} {mystage.properties}

That's it. You now have a pipeline configured with a SetStaticField-stage. If your Hydra Core was running while you configured this, you'll notice that it picked up the change and launched the stage with the properties you provided.

Next, you'll probably want to add your SolrOutputStage, and then start pushing some documents in!