DataStax Enterprise 3.0 Documentation

Running the demo

This documentation corresponds to an earlier product version. Make sure this document corresponds to your version.

Latest DSE documentation | Earlier DSE documentation

You need to start a DataStax Enterprise node as a Solr node to run the demo. You can run the demo in these ways:

You can run Solr on one or more nodes. DataStax does not support running Solr and Hadoop on the same node, although it's possible to do so in a development environment. In production environments, run Solr and Hadoop on separate nodes.

Starting a Solr node

Follow these steps to start DSE Search/Solr on a single node.

  1. Start DSE as a Solr node.

  2. In another shell, check that your Cassandra ring is up and running. For example, on a Mac:

    • RHEL or Debian installations

      dsetool ring -h localhost
    • Tar distribution, such as Mac

      cd <install_location>/bin
      ./dsetool ring -h localhost

    A table of information appears showing the state of the node and identifying it as a Solr node.

Now, set up and run the DSE search demo.

Running the demo

After starting DSE as a Solr node, open a shell window or tab, and follow these steps to run the demo.

  1. Make the wikipedia demo directory your current directory. The location of the demo directory depends on your platform:

    • RHEL or Debian installations

      cd  /usr/share/dse-demos/wikipedia
    • Tar distribution

      cd <install_location>/demos/wikipedia
  2. Upload the schema.


    The script posts solrconfig.xml and schema.xml to these locations:

    wiki.solr in the URL creates the keyspace (wiki) and the column family (solr) in Cassandra. The script also creates the Solr index and core.

  3. Index the articles contained in the wikipedia-sample.bz2 file in the demo directory:

    ./ --wikifile wikipedia-sample.bz2

    Three thousand articles load.

  4. To see a sample Wikipedia search UI, open your web browser and go to:


  5. Inspect the index keyspace, wiki, using the Solr Admin tool:


    Be sure to enter the trailing "/".

  6. Inspect the column family, solr. In the Solr Admin tool, click wiki.solr to inspect the schema.


Running DSE Search/Solr demos using legacy data

DataStax 3.0.x adds an the dseTypeMappingVersion element to the solrconfig.xml of the DSE Search/Solr demos:

  • Solr wikipedia demo
  • Log search demo
  • Solr stress demo

To use data from an earlier release, you need to use the default legacy type mapping. Disable the new Solr type mappings in the solrconfig.xml files of the demos by following these steps.

To run demos using data from an earlier release

  1. Make the default legacy type mapping effective by commenting out the dseTypeMappingVersion element.

    <!-- <dseTypeMappingVersion>1</dseTypeMappingVersion> -->

    You can also use 0 instead of 1 for the version.

  2. Delete the wikipedia data in Cassandra database and the Solr index.

  3. Upload the solrconfig.xml and schema.xml.

    curl http://localhost:8983/solr/resource/wiki.solr/solrconfig.xml --data-binary @solrconfig.xml -H 'Content-type:text/xml; charset=utf-8'
    curl http://localhost:8983/solr/resource/wiki.solr/schema.xml --data-binary @schema.xml -H 'Content-type:text/xml; charset=utf-8'
  4. Reload the core

    curl "http://localhost:8983/solr/admin/cores?action=RELOAD&name=wiki.solr"

    Attempting to load a solrconfig with a different dseTypeMappingVersion configuration and reloading the core causes an error.

  5. Index the articles contained in the wikipedia-sample.bz2 file in the demo directory:

    ./ --wikifile wikipedia-sample.bz2

Running the demo on a secure cluster

You can run the wikipedia, stress, and log search demos on a secure cluster. Additional options you need to set are:

  • Kerberos Options
    • -a enable Kerberos authentication
    • -h <hostname> server hostname (not required if server hostname resolution is correctly set up)
  • HTTP Basic Authentication (not recommended for production)
    • -u username
    • -p password
  • SSL Options
    • -e <cert> enable https for client to node encryption, using <cert> certificate file
    • -k disable strict hostname checking for ssl certificates