Wikidata Query Service/Implementation

Labs Deployment (beta)
Note that currently deployment is via git-fat (see below) which means it may not work on labs. In that case the scripts have to be deployed manually. This can be done as follows: See also Wikidata Query service beta.
 * 1) Check out   repository
 * 2) Run git-fat pull to instantiate the binaries
 * 3) rsync the files to deploy directory

Production Deployment
Production deployment is done via git deployment repository. The procedure is as follows: The puppet role that needs to be enabled for the service is.
 * 1)   the source repository.
 * 2)   in the source repository - this deploys the artifacts to archiva. Note that for this you will need repositories   and   configured in   with archiva username/password.
 * 3) Install new files (which will be also in  ) to deploy repo above. Commit them. Note that since git-fat uses archiva as primary storage, there can be a delay between files being deployed to archiva and them appearing on rsync and ready for git-fat deployment.
 * 4) Run deploy procedure as described in Trebuchet docs.

Services
Service  runs the Blazegraph server.

Service  runs the updater. Depends on wdqs-blazegraph.

Upgrading Blazegraph

 * 1) Use script buildwmf.sh to create Blazegraph binaries. Note that you need to update   in the script. Also note that   should point to Java 7 home directory (production hosts do not have Java 8 yet).
 * 2) Use instructions in source repo to upload the new binaries to archiva.
 * 3) Update Blazegraph version in   in the source.
 * 4) Rebuild/redeploy production packages as described above.

Releasing to Maven
Release procedure described here: http://central.sonatype.org/pages/ossrh-guide.html

Updating specific ID
If there is a need to update specific ID data manually, this can be done using (for ID Q12345):

The runUpdate.sh script is located in the root of WDQS deployment directory

Contacts
If you need more info, talk to User:Smalyshev_(WMF) or anybody from Discovery team.