A simple Solr package for a question answering engine

• Start Solr (version 8.4 or later) nodes with -Denable.packages=true

  bin/solr -c -Denable.packages=true

• Add repository:

  bin/solr package add-repo gerlowskija-jaxrs "https://raw.githubusercontent.com/gerlowskija/jax-rs-solr-plugins/master/repo/"

• See available packages:

  bin/solr package list-available

• Install the package

  bin/solr package install jaxrs-plugins

• Create a collection

  curl "http://localhost:8983/solr/admin/collections?action=CREATE&name=plugintestcoll&numShards=1"

• Deploy package on the collection

  bin/solr package deploy jaxrs-plugins -y -collections plugintestcoll -p RH-HANDLER-PATH=/somecorepathv1

• Use the plugins V2 API

  curl "http://localhost:8983/api/collections/plugintestcoll/somecorepath"

You need to follow the prerequisites one time, and release process everytime you wish to release a new package.

• Create your private key/public key pair to sign your packages:

  openssl genrsa -out privatekey.pem 512 && openssl rsa -in privatekey.pem -pubout -outform DER -out publickey.der

• Keep your privatekey.pem securely and outside of your Git repository. This will be used to sign all future releases of your packages.

• Place your publickey.der file in the repo/ folder.

• Please note that if a repository has already been added in Solr, but the public key changes (as it would if you follow the above steps), you would need to add the repository again (maybe with some other name than that was previously added, chatman-qa in this case).

• Increase the version in pom.xml. Adjust the src/resources/manifest.json, if needed.

• Do mvn package, which will place the new jar in repo directory.

• Sign the jar with your private key:

  openssl dgst -sha1 -sign <path-to-privatekey.pem> <new-jar-file> | openssl enc -base64

• Add a section in repo/repository.json file with the release details. The signature will be same as output from previous command (but concatenate the multiline output into a single string, without any whitespace).

• Add, commit, push your changes to the repo/ folder. Test your release by bin/solr package list-available on a Solr instance where this repository has been added already.