Conventions

In this book, you will find a number of text styles that distinguishes between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "The lib entry in the solrconfig.xml file tells Solr to look for all the JAR files from the ../../langid directory."

A block of code is set as follows:

<field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />
<field name="name" type="text_general" indexed="true" stored="true"/>
<field name="description" type="text_general" indexed="true" stored="true" />
<field name="langId" type="string" indexed="true" stored="true" />

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

<field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />
<field name="name" type="text_general" indexed="true" stored="true"/>
<field name="description" type="text_general" indexed="true" stored="true" />
<field name="langId" type="string" indexed="true" stored="true" />

Any command-line input or output is written as follows:

curl 'localhost:8983/solr/update?commit=true' -H 'Content-type:application/json' -d '[{"id":"1","file":{"set":"New file name"}}]'

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "The Overview page for a collection gives you basic statistics about the core of the collection such as number of documents, heap memory usage, version of the index, number of segments, and so on."