lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r803742 - in /websites/staging/lucene/trunk/content: css/solr.css solr/tutorial.html
Date Wed, 01 Feb 2012 19:59:56 GMT
Author: buildbot
Date: Wed Feb  1 19:59:56 2012
New Revision: 803742

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/css/solr.css
    websites/staging/lucene/trunk/content/solr/tutorial.html

Modified: websites/staging/lucene/trunk/content/css/solr.css
==============================================================================
--- websites/staging/lucene/trunk/content/css/solr.css (original)
+++ websites/staging/lucene/trunk/content/css/solr.css Wed Feb  1 19:59:56 2012
@@ -932,5 +932,32 @@ body#full #wrap {
     display: block;
     white-space: pre;
     vertical-align: middle;
+    width: 99%;
+    padding-left: 5px;
+    padding-bottom: 0px;
+    padding-right: 5px;
+    padding-top: 0px;
+}
 
+/*
+code {
+    margin: 5px 0;
+    padding: 15px;
+    text-align: left;
+    display: block;
+    overflow: auto;
+    font: 500 1em/ 1.5em 'Lucida Console', 'courier new', monospace;
+    border: 1px solid #ECF8FE;
+    background: #ECF8FE;
+    }
+*/
+
+.tutorial code.inline{
+    font: 0.9em;
+    display: inline;
+    margin: 0px 0;
+    padding: 0px;
+    font-weight: bold;
+    background-color: white;
+    border-color: white;
 }
\ No newline at end of file

Modified: websites/staging/lucene/trunk/content/solr/tutorial.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/tutorial.html (original)
+++ websites/staging/lucene/trunk/content/solr/tutorial.html Wed Feb  1 19:59:56 2012
@@ -223,7 +223,7 @@ schema, and some sample data.</p>
 <a href="http://openjdk.java.net/">Open JDK</a>,
 <a href="http://www.ibm.com/developerworks/java/jdk/">IBM</a>, or
 <br/>
-Running <code>java -version</code> at the command line should indicate a version
+Running <code class="inline">java -version</code> at the command line should
indicate a version
 number starting with 1.6.  Gnu's GCJ is not supported and does not work with Solr.</p>
 </li>
 <li>
@@ -235,7 +235,7 @@ number starting with 1.6.  Gnu's GCJ is 
 Please run the browser showing this tutorial and the Solr server on the same machine so tutorial
links will correctly point to your Solr server.
 </em></p>
 <p>Begin by unziping the Solr release and changing your working directory
-to be the "<code>example</code>" directory.  (Note that the base directory name
may vary with the version of Solr downloaded.)  For example, with a shell in UNIX, Cygwin,
or MacOS:</p>
+to be the "<code  class="inline">example</code>" directory.  (Note that the base
directory name may vary with the version of Solr downloaded.)  For example, with a shell in
UNIX, Cygwin, or MacOS:</p>
 <div class="cmd">
     user:~solr$ ls
     solr-nightly.zip
@@ -245,7 +245,7 @@ to be the "<code>example</code>" directo
 
 <p>Solr can run in any Java Servlet Container of your choice, but to simplify
 this tutorial, the example index includes a small installation of Jetty.</p>
-<p>To launch Jetty with the Solr WAR, and the example configs, just run the <code>start.jar</code>
...</p>
+<p>To launch Jetty with the Solr WAR, and the example configs, just run the <code
 class="inline">start.jar</code> ...</p>
 <div class="cmd">
     user:~/solr/example$ java -jar start.jar
     2009-10-23 16:42:53.816::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
@@ -268,17 +268,18 @@ modify a Solr index by POSTing XML Docum
 update) documents, delete documents, commit pending adds and deletes, and
 optimize your index.<br />
 </p>
-<p>The <code>exampledocs</code> directory contains samples of the types
of
+<p>The <code class="inline">exampledocs</code> directory contains samples
of the types of
 instructions Solr expects, as well as a java utility for posting them from the
-command line (a <code>post.sh</code> shell script is also available, but for
+command line (a <code  class="inline">post.sh</code> shell script is also available,
but for
 this tutorial we'll use the cross-platform Java client).    To try this,
 open a new terminal window, enter the exampledocs directory, and run
-"<code>java -jar post.jar</code>" on some of the XML files in that directory,
+"<code  class="inline">java -jar post.jar</code>" on some of the XML files in
that directory,
 indicating the URL of the Solr server:</p>
 <div class="cmd">
     user:~/solr/example/exampledocs$ java -jar post.jar solr.xml monitor.xml
     SimplePostTool: version 1.2
-    SimplePostTool: WARNING: Make sure your XML documents are encoded in UTF-8, other encodings
are not currently supported
+    SimplePostTool: WARNING: Make sure your XML documents are encoded in UTF-8, \
+              other encodings are not currently supported
     SimplePostTool: POSTing files to http://localhost:8983/solr/update..
     SimplePostTool: POSTing file solr.xml
     SimplePostTool: POSTing file monitor.xml
@@ -293,7 +294,8 @@ Clicking the "Search" button should take
 <div class="cmd">
     user:~/solr/example/exampledocs$ java -jar post.jar *.xml
     SimplePostTool: version 1.2
-    SimplePostTool: WARNING: Make sure your XML documents are encoded in UTF-8, other encodings
are not currently supported
+    SimplePostTool: WARNING: Make sure your XML documents are encoded in UTF-8, \
+                other encodings are not currently supported
     SimplePostTool: POSTing files to http://localhost:8983/solr/update..
     SimplePostTool: POSTing file hd.xml
     SimplePostTool: POSTing file ipod_other.xml
@@ -339,25 +341,25 @@ programatically create documents to send
 </li>
 </ul>
 <h2 id="updating_data">Updating Data</h2>
-<p>You may have noticed that even though the file <code>solr.xml</code>
has now
+<p>You may have noticed that even though the file <code  class="inline">solr.xml</code>
has now
 been POSTed to the server twice, you still only get 1 result when searching for
 "solr".  This is because the example schema.xml specifies a "uniqueKey" field
-called "<code>id</code>".  Whenever you POST instructions to Solr to add a
+called "<code  class="inline">id</code>".  Whenever you POST instructions to
Solr to add a
 document with the same value for the uniqueKey as an existing document, it
 automatically replaces it for you.  You can see that that has happened by
-looking at the values for <code>numDocs</code> and <code>maxDoc</code>
in the
+looking at the values for <code  class="inline">numDocs</code> and <code 
class="inline">maxDoc</code> in the
 "CORE"/searcher section of the statistics page...<br />
 </p>
 <p><a href="http://localhost:8983/solr/admin/stats.jsp">http://localhost:8983/solr/admin/stats.jsp</a></p>
 <p><em>numDocs</em> represents the number of searchable documents in the
 index (and will be larger than the number of XML files since some files
-contained more than one <code>&lt;doc&gt;</code>). <em>maxDoc</em>
+contained more than one <code  class="inline">&lt;doc&gt;</code>). <em>maxDoc</em>
 may be larger as the maxDoc count includes logically deleted documents that
 have not yet been removed from the index. You can re-post the sample XML
 files over and over again as much as you want and numDocs will never
 increase,because the new documents will constantly be replacing the old.</p>
 <p>Go ahead and edit the existing XML files to change some of the data, and re-run
-the <code>java -jar post.jar</code> command, you'll see your changes reflected
+the <code  class="inline">java -jar post.jar</code> command, you'll see your
changes reflected
 in subsequent searches.</p>
 <h2 id="deleting_data">Deleting Data</h2>
 <p>You can delete data by POSTing a delete command to the update URL and specifying
the value
@@ -365,16 +367,16 @@ in subsequent searches.</p>
   are smaller, we will specify them right on the command line rather than reference an XML
file.</p>
 <p>Execute the following command to delete a document</p>
 <div class="cmd">
-    java -Ddata=args -Dcommit=no -jar post.jar "<delete><id>SP2514N</id></delete>"
+java -Ddata=args -Dcommit=no -jar post.jar "&lt;delete&gt;&lt;id&gt;SP2514N&lt;/id&lt;&gt;/delete&gt;"
 </div>
 
 <p>Now if you go to the <a href="http://localhost:8983/solr/admin/stats.jsp">statistics</a>
page and scroll down
-   to the UPDATE_HANDLERS section and verify that "<code>deletesById : 1</code>"
+   to the UPDATE_HANDLERS section and verify that "<code class="inline">deletesById
: 1</code>"
 If you search for <a href="http://localhost:8983/solr/select?q=id:SP2514N">id:SP2514N</a>
it will still be found,
    because index changes are not visible until, and a new searcher is opened.  To cause
    this to happen, send a commit command to Solr (post.jar does this for you by default):</p>
 <div class="cmd">
-    java -jar post.jar
+java -jar post.jar
 </div>
 
 <p>Now re-execute the previous search and verify that no matching documents are found.
 Also revisit the
@@ -382,16 +384,16 @@ statistics page and observe the changes 
 Here is an example of using delete-by-query to delete anything with
   <a href="http://localhost:8983/solr/select?q=name:DDR&amp;fl=name">DDR</a>
in the name:</p>
 <div class="cmd">
-    java -Ddata=args -jar post.jar "<delete><query>name:DDR</query></delete>"
+java -Ddata=args -jar post.jar "<delete><query>name:DDR</query></delete>"
 </div>
 
 <p>Commit can be an expensive operation so it's best to make many changes to an index
in a batch and
   then send the commit command at the end.  There is also an optimize command that does the
same thing as commit,
   in addition to merging all index segments into a single segment, making it faster to search
and causing any
   deleted documents to be removed.  All of the update commands are documented <a href="http://wiki.apache.org/solr/UpdateXmlMessages">here</a>.</p>
-<p>To continue with the tutorial, re-add any documents you may have deleted by going
to the <code>exampledocs</code> directory and executing</p>
+<p>To continue with the tutorial, re-add any documents you may have deleted by going
to the <code class="inline">exampledocs</code> directory and executing</p>
 <div class="cmd">
-    java -jar post.jar *.xml
+java -jar post.jar *.xml
 </div>
 
 <h2 id="querying_data">Querying Data</h2>
@@ -428,14 +430,14 @@ that allows setting the various request 
 <ul>
 <li><a href="http://localhost:8983/solr/select/?indent=on&amp;q=*:*&amp;sort=div(popularity,add(price,1))+desc">q=video&amp;sort=div(popularity,add(price,1))
desc</a></li>
 </ul>
-<p>If no sort is specified, the default is <code>score desc</code> to return
the matches having the highest relevancy.</p>
+<p>If no sort is specified, the default is <code class="inline">score desc</code>
to return the matches having the highest relevancy.</p>
 <h2 id="highlighting">Highlighting</h2>
 <p>Hit highlighting returns relevent snippets of each returned document, and highlights
 keywords from the query within those context snippets.</p>
-<p>The following example searches for <code>video card</code> and requests
-highlighting on the fields <code>name,features</code>.  This causes a
-<code>highlighting</code> section to be added to the response with the
-words to highlight surrounded with <code>&lt;em&gt;</code> (for emphasis)
+<p>The following example searches for <code class="inline">video card</code>
and requests
+highlighting on the fields <code class="inline">name,features</code>.  This causes
a
+<code class="inline">highlighting</code> section to be added to the response
with the
+words to highlight surrounded with <code class="inline">&lt;em&gt;</code>
(for emphasis)
 tags.</p>
 <p><a href="http://localhost:8983/solr/select/?wt=json&amp;indent=on&amp;q=video+card&amp;fl=name,id&amp;hl=true&amp;hl.fl=name,features">...&amp;q=video
card&amp;fl=name,id&amp;hl=true&amp;hl.fl=name,features</a></p>
 <p>More request parameters related to controlling highlighting may be found
@@ -446,19 +448,19 @@ tags.</p>
 <p>Faceted search takes the documents matched by a query and generates counts for various
 properties or categories.  Links are usually provided that allows users to "drill down" or
 refine their search results based on the returned categories.</p>
-<p>The following example searches for all documents (<code><em>:</em></code>)
and
-requests counts by the category field <code>cat</code>.</p>
+<p>The following example searches for all documents (<code class="inline"><em>:</em></code>)
and
+requests counts by the category field <code class="inline">cat</code>.</p>
 <p><a href="http://localhost:8983/solr/select/?wt=json&amp;indent=on&amp;q=*:*&amp;fl=name&amp;facet=true&amp;facet.field=cat">...&amp;q=<em>:</em>&amp;facet=true&amp;facet.field=cat</a></p>
 <p>Notice that although only the first 10 documents are returned in the results list,
 the facet counts generated are for the complete set of documents that match the query.</p>
 <p>We can facet multiple ways at the same time.  The following example adds a facet
on the
-boolean <code>inStock</code> field:</p>
+boolean <code class="inline">inStock</code> field:</p>
 <p><a href="http://localhost:8983/solr/select/?wt=json&amp;indent=on&amp;q=*:*&amp;fl=name&amp;facet=true&amp;facet.field=cat&amp;facet.field=inStock">...&amp;q=<em>:</em>&amp;facet=true&amp;facet.field=cat&amp;facet.field=inStock</a></p>
 <p>Solr can also generate counts for arbitrary queries. The following example
-queries for <code>ipod</code> and shows prices below and above 100 by using
+queries for <code class="inline">ipod</code> and shows prices below and above
100 by using
 range queries on the price field.</p>
 <p><a href="http://localhost:8983/solr/select/?wt=json&amp;indent=on&amp;q=ipod&amp;fl=name&amp;facet=true&amp;facet.query=price:[0+TO+100]&amp;facet.query=price:[100+TO+*]">...&amp;q=ipod&amp;facet=true&amp;facet.query=price:[0
TO 100]&amp;facet.query=price:[100 TO *]</a></p>
-<p>One can even facet by date ranges.  This example requests counts for the manufacture
date (<code>manufacturedate_dt</code> field) for each year between 2004 and 2010.</p>
+<p>One can even facet by date ranges.  This example requests counts for the manufacture
date (<code class="inline">manufacturedate_dt</code> field) for each year between
2004 and 2010.</p>
 <p><a href="http://localhost:8983/solr/select/?wt=json&amp;indent=on&amp;q=*:*&amp;fl=name,manufacturedate_dt&amp;facet=true&amp;facet.date=manufacturedate_dt&amp;facet.date.start=2004-01-01T00:00:00Z&amp;facet.date.end=2010-01-01T00:00:00Z&amp;facet.date.gap=%2b1YEAR">...&amp;q=<em>:</em>&amp;facet=true&amp;facet.date=manufacturedate_dt&amp;facet.date.start=2004-01-01T00:00:00Z&amp;facet.date.end=2010-01-01T00:00:00Z&amp;facet.date.gap=+1YEAR</a></p>
 <p>More information on faceted search may be found on the 
 <a href="http://wiki.apache.org/solr/SolrFacetingOverview">faceting overview</a>
@@ -484,26 +486,26 @@ applied to any queries in order to match
 <li>
 <p>A search for
    <a href="http://localhost:8983/solr/select/?indent=on&amp;q=power-shot&amp;fl=name">power-shot</a>
-   matches <code>PowerShot</code>, and
+   matches <code class="inline">PowerShot</code>, and
   <a href="http://localhost:8983/solr/select/?indent=on&amp;q=adata&amp;fl=name">adata</a>
-  matches <code>A-DATA</code> due to the use of WordDelimiterFilter and LowerCaseFilter.</p>
+  matches <code class="inline">A-DATA</code> due to the use of WordDelimiterFilter
and LowerCaseFilter.</p>
 </li>
 <li>
 <p>A search for
   <a href="http://localhost:8983/solr/select/?indent=on&amp;q=features:recharging&amp;fl=name,features">features:recharging</a>
-   matches <code>Rechargeable</code> due to stemming with the EnglishPorterFilter.</p>
+   matches <code class="inline">Rechargeable</code> due to stemming with the
EnglishPorterFilter.</p>
 </li>
 <li>
 <p>A search for
    <a href="http://localhost:8983/solr/select/?indent=on&amp;q=&quot;1 gigabyte&quot;&amp;fl=name">"1
gigabyte"</a>
-   matches things with <code>GB</code>, and the misspelled
+   matches things with <code class="inline">GB</code>, and the misspelled
   <a href="http://localhost:8983/solr/select/?indent=on&amp;q=pixima&amp;fl=name">pixima</a>
-   matches <code>Pixma</code> due to use of a SynonymFilter.</p>
+   matches <code class="inline">Pixma</code> due to use of a SynonymFilter.</p>
 </li>
 </ul>
 <p>The <a href="http://wiki.apache.org/solr/SchemaXml">schema</a> defines
 the fields in the index and what type of analysis is applied to them.  The current schema
your server is using
-may be accessed via the <code>[SCHEMA]</code> link on the <a href="http://localhost:8983/solr/admin/">admin</a>
page.</p>
+may be accessed via the <code class="inline">[SCHEMA]</code> link on the <a
href="http://localhost:8983/solr/admin/">admin</a> page.</p>
 <p>A full description of the analysis components, Analyzers, Tokenizers, and TokenFilters
 available for use is <a href="http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters">here</a>.</p>
 <h2 id="analysis_debugging">Analysis Debugging</h2>
@@ -511,10 +513,10 @@ available for use is <a href="http://wik
   debugging page where you can see how a text value is broken down into words,
   and shows the resulting tokens after they pass through each filter in the chain.</p>
 <p><a href="http://localhost:8983/solr/admin/analysis.jsp?name=name&amp;val=Canon+Power-Shot+SD500">This</a>
-  shows how "<code>Canon Power-Shot SD500</code>" would be indexed as a value
in the name field.  Each row of
-  the table shows the resulting tokens after having passed through the next TokenFilter in
the Analyzer for the <code>name</code> field.
-  Notice how both <code>powershot</code> and <code>power</code>,
<code>shot</code> are indexed.  Tokens generated at the same position
-  are shown in the same column, in this case <code>shot</code> and <code>powershot</code>.</p>
+  shows how "<code class="inline">Canon Power-Shot SD500</code>" would be indexed
as a value in the name field.  Each row of
+  the table shows the resulting tokens after having passed through the next TokenFilter in
the Analyzer for the <code class="inline">name</code> field.
+  Notice how both <code class="inline">powershot</code> and <code class="inline">power</code>,
<code class="inline">shot</code> are indexed.  Tokens generated at the same position
+  are shown in the same column, in this case <code class="inline">shot</code>
and <code class="inline">powershot</code>.</p>
 <p>Selecting <a href="http://localhost:8983/solr/admin/analysis.jsp?name=name&amp;verbose=on&amp;val=Canon+Power-Shot+SD500">verbose
output</a>
 will show more details, such as the name of each analyzer component in the chain, token positions,
and the start and end positions
 of the token in the original text.</p>



Mime
View raw message