You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@manifoldcf.apache.org by kw...@apache.org on 2010/07/08 17:01:10 UTC
svn commit: r961792 - in /incubator/lcf/site: publish/ publish/images/
src/documentation/content/xdocs/ src/documentation/resources/images/
Author: kwright
Date: Thu Jul 8 15:01:08 2010
New Revision: 961792
URL: http://svn.apache.org/viewvc?rev=961792&view=rev
Log:
Update site to reflect latest solr connector changes.
Added:
incubator/lcf/site/publish/images/solr-configure-schema.PNG (with props)
incubator/lcf/site/publish/images/solr-job-field-mapping.PNG (with props)
incubator/lcf/site/src/documentation/resources/images/solr-configure-schema.PNG (with props)
incubator/lcf/site/src/documentation/resources/images/solr-job-field-mapping.PNG (with props)
Modified:
incubator/lcf/site/publish/developer-resources.pdf
incubator/lcf/site/publish/end-user-documentation.html
incubator/lcf/site/publish/end-user-documentation.pdf
incubator/lcf/site/publish/faq.pdf
incubator/lcf/site/publish/images/solr-configure-arguments.PNG
incubator/lcf/site/publish/images/solr-configure-server.PNG
incubator/lcf/site/publish/images/solr-status.PNG
incubator/lcf/site/publish/index.pdf
incubator/lcf/site/publish/linkmap.pdf
incubator/lcf/site/publish/mail.pdf
incubator/lcf/site/publish/who.pdf
incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml
incubator/lcf/site/src/documentation/resources/images/solr-configure-arguments.PNG
incubator/lcf/site/src/documentation/resources/images/solr-configure-server.PNG
incubator/lcf/site/src/documentation/resources/images/solr-status.PNG
Modified: incubator/lcf/site/publish/developer-resources.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/developer-resources.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/end-user-documentation.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/end-user-documentation.html?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
--- incubator/lcf/site/publish/end-user-documentation.html (original)
+++ incubator/lcf/site/publish/end-user-documentation.html Thu Jul 8 15:01:08 2010
@@ -837,7 +837,7 @@ document.write("Last Published: " + docu
<p>Unfortunately, this lack of specificity comes at a cost. Unless you take care to filter documents properly in each job, large movie files or other opaque
content may well be picked up and sent to Solr for indexing, which will greatly increase the dead load on the overall system. It is therefore a good idea to review
all crawls done through a Solr connection while they are underway, to be sure there isn't a misconfiguration of this kind.</p>
-<p>When you create a Solr output connection, two configuration tabs appear. The "Server" tab allows you to configure the HTTP target of the connection:</p>
+<p>When you create a Solr output connection, three configuration tabs appear. The "Server" tab allows you to configure the HTTP target of the connection:</p>
<br>
<br>
<div id="" style="text-align: center;">
@@ -846,7 +846,15 @@ document.write("Last Published: " + docu
<br>
<p>Fill in the fields according to your Solr configuration. The Solr connection type supports only basic authentication at this time; if you have this enabled, supply the credentials
as requested on the bottom part of the form.</p>
-<p>The second tab is the "Arguments" tab, which allows you to specify arbitrary arguments to be sent to Solr. This is a popular way of telling Solr how to handle
+<p>The second tab is the "Schema" tab, which allows you to specify the name of the Solr field to use as a document identifier. The Solr connection type will treat
+ this field as being a unique key for locating the indexed document for further modification or deletion:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="Solr Configuration, Schema tab" src="images/solr-configure-schema.PNG" width="80%"></div>
+<br>
+<br>
+<p>The third tab is the "Arguments" tab, which allows you to specify arbitrary arguments to be sent to Solr. This is a popular way of telling Solr how to handle
specific documents, so the connection type allows you to add arguments to each Solr indexing request:</p>
<br>
<br>
@@ -865,10 +873,19 @@ document.write("Last Published: " + docu
<br>
<br>
<p>Note that in this example, the Solr connection is not responding, which is leading to an error status message instead of "Connection working".</p>
-<p>When you configure a job to use a Solr-type output connection, no Solr-specific additional tabs appear at this time. In the future, this may well change, and job-specific
- tabs could be added, most likely to allow job-specific arguments to be added to each index request. If functionality of this kind seems important to your application,
- please do not hesitate to contact the Lucene Connectors Framework team with your request.</p>
-<a name="N103C4"></a><a name="gtsoutputconnector"></a>
+<p>When you configure a job to use a Solr-type output connection, the Solr connection type provides a tab called "Field Mapping". The purpose of this tab
+ is to allow you to map metadata fields as fetched by the job's connection type to fields that Solr is set up to receive. This is necessary because
+ the names of the metadata items are often determined by the repository, with no alignment to fields defined in the Solr schema. You may also
+ suppress specific metadata items from being sent to the index using this tab. The tab looks like this:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="Solr Specification, Field Mapping tab" src="images/solr-job-field-mapping.PNG" width="80%"></div>
+<br>
+<br>
+<p>Add a new mapping by filling in the "source" with the name of the metadata item from the repository, and "target" as the name of the output field in
+ Solr, and click the "Add" button. Leaving the "target" field blank will result in all metadata items of that name not being sent to Solr.</p>
+<a name="N103E0"></a><a name="gtsoutputconnector"></a>
<h3 class="h4">MetaCarta GTS Output Connection</h3>
<p>The MetaCarta GTS output connection type is designed to allow Lucene Connectors Framework to submit documents to an appropriate MetaCarta GTS search
appliance, via the appliance's HTTP Ingestion API.</p>
@@ -877,7 +894,7 @@ document.write("Last Published: " + docu
<p>When you configure a job to use a GTS-type output connection, two additional tabs will be presented to the user: "Collections" and "Document Templates". These
tabs allow per-job specification of these GTS-specific features.</p>
<p>More here later</p>
-<a name="N103D7"></a><a name="nulloutputconnector"></a>
+<a name="N103F3"></a><a name="nulloutputconnector"></a>
<h3 class="h4">Null Output Connection</h3>
<p>The null output connection type is meant primarily to function as an aid for people writing repository connection types. It is not expected to be useful in practice.</p>
<p>The null output connection type simply logs indexing and deletion requests, and does nothing else. It does not have any special configuration tabs, nor does it
@@ -885,10 +902,10 @@ document.write("Last Published: " + docu
</div>
-<a name="N103E5"></a><a name="authorityconnectiontypes"></a>
+<a name="N10401"></a><a name="authorityconnectiontypes"></a>
<h2 class="h3">Authority Connection Types</h2>
<div class="section">
-<a name="N103EB"></a><a name="adauthority"></a>
+<a name="N10407"></a><a name="adauthority"></a>
<h3 class="h4">Active Directory Authority Connection</h3>
<p>An active directory authority connection is essential for enforcing security for documents from Windows shares, Microsoft SharePoint, and IBM FileNet repositories.
This connection type needs to be provided with information about how to log into an appropriate Windows domain controller, with a user that has sufficient privileges to
@@ -922,7 +939,7 @@ document.write("Last Published: " + docu
<br>
<br>
<p>Note that in this example, the Active Directory connection is not responding, which is leading to an error status message instead of "Connection working".</p>
-<a name="N10424"></a><a name="livelinkauthority"></a>
+<a name="N10440"></a><a name="livelinkauthority"></a>
<h3 class="h4">OpenText LiveLink Authority Connection</h3>
<p>A LiveLink authority connection is needed to enforce security for documents retrieved from LiveLink repositories.</p>
<p>In order to function, this connection type needs to be provided with
@@ -961,7 +978,7 @@ document.write("Last Published: " + docu
<br>
<p>We suggest that you examine the status carefully and correct any reported errors before proceeding. Note that in this example, the LiveLink server would not accept connections, which
is leading to an error status message instead of "Connection working".</p>
-<a name="N10476"></a><a name="documentumauthority"></a>
+<a name="N10492"></a><a name="documentumauthority"></a>
<h3 class="h4">EMC Documentum Authority Connection</h3>
<p>A Documentum authority connection is required for enforcing security for documents retrieved from Documentum repositories.</p>
<p>This connection type needs to be provided with information about what Content Server to connect to, and the credentials that should be used to retrieve a user's ACLs from that machine.
@@ -1010,7 +1027,7 @@ document.write("Last Published: " + docu
<br>
<p>Pay careful attention to the status, and be prepared to correct any
problems that are displayed.</p>
-<a name="N104CA"></a><a name="memexauthority"></a>
+<a name="N104E6"></a><a name="memexauthority"></a>
<h3 class="h4">Memex Patriarch Authority Connection</h3>
<p>A Memex authority connection is required for enforcing security for documents retrieved from Memex repositories.</p>
<p>This connection type needs to be provided with information about what Memex Server to connect to, and what user mapping to perform.
@@ -1047,7 +1064,7 @@ document.write("Last Published: " + docu
<br>
<p>We suggest that you examine the status carefully and correct any reported errors before proceeding. Note that in this example, the Memex server has a license error, which
is leading to an error status message instead of "Connection working".</p>
-<a name="N10519"></a><a name="meridioauthority"></a>
+<a name="N10535"></a><a name="meridioauthority"></a>
<h3 class="h4">Autonomy Meridio Authority Connection</h3>
<p>A Meridio authority connection is required for enforcing security for documents retrieved from Meridio repositories.</p>
<p>This connection type needs to be provided with information about what Document Server to connect to, what Records Server to connect to, and what User Service Server
@@ -1124,10 +1141,10 @@ document.write("Last Published: " + docu
</div>
-<a name="N105A1"></a><a name="repositoryconnectiontypes"></a>
+<a name="N105BD"></a><a name="repositoryconnectiontypes"></a>
<h2 class="h3">Repository Connection Types</h2>
<div class="section">
-<a name="N105A7"></a><a name="filesystemrepository"></a>
+<a name="N105C3"></a><a name="filesystemrepository"></a>
<h3 class="h4">Generic File System Repository Connection</h3>
<p>The generic file system repository connection type was developed primarily as an example, demonstration, and testing tool, although it can potentially be useful for indexing local
files that exist on the same machine that Lucene Connectors Framework is running on. Bear in mind that there is no support in this connection type for any kind of
@@ -1166,7 +1183,7 @@ document.write("Last Published: " + docu
may then add rules to it. Each rule has a match expression, an indication of whether the rule is intended to match files or directories, and an action (include or exclude).
Rules are evaluated from top to bottom, and the first rule that matches the file name is the one that is chosen. To add a rule, select the desired pulldowns, type in
a match file specification (e.g. "*.txt"), and click the "Add" button.</p>
-<a name="N105DF"></a><a name="rssrepository"></a>
+<a name="N105FB"></a><a name="rssrepository"></a>
<h3 class="h4">Generic RSS Repository Connection</h3>
<p>The RSS connection type is specifically designed to crawl RSS feeds. While the Web connection type can also extract links from RSS feeds, the RSS connection type
differs in the following ways:</p>
@@ -1379,7 +1396,7 @@ document.write("Last Published: " + docu
<br>
<br>
<p>Select the mode you want the connection to operate in.</p>
-<a name="N10762"></a><a name="webrepository"></a>
+<a name="N1077E"></a><a name="webrepository"></a>
<h3 class="h4">Generic Web Repository Connection</h3>
<p>The Web connection type is effectively a reasonably full-featured web crawler. It is capable of handling most kinds of authentication (basic, all forms of NTLM,
and session-based), and can extract links from the following kinds of documents:</p>
@@ -1662,7 +1679,7 @@ document.write("Last Published: " + docu
<br>
<br>
<p>Enter the name of the desired metadata on the left, and the desired value (if any) on the right, and click the "Add" button.</p>
-<a name="N1093B"></a><a name="jcifsrepository"></a>
+<a name="N10957"></a><a name="jcifsrepository"></a>
<h3 class="h4">Windows Share/DFS Repository Connection</h3>
<p>The Windows Share connection type allows you to access content stored on Windows shares, even from non-Windows systems. Also supported are Samba and various
third-party Network Attached Storage servers.</p>
@@ -1785,7 +1802,7 @@ document.write("Last Published: " + docu
<p>The mappings specified here are similar in all respects to the path attribute mapping setup described above. If no mappings are present, the file path is converted
to a canonical file IRI. If mappings are present, the conversion is presumed to produce a valid URL, which can be used to access the document via some
variety of Windows Share http server.</p>
-<a name="N10A09"></a><a name="jdbcrepository"></a>
+<a name="N10A25"></a><a name="jdbcrepository"></a>
<h3 class="h4">Generic Database Repository Connection</h3>
<p>The generic database connection type allows you to index content from a database table, served by one of the following databases:</p>
<br>
@@ -1976,10 +1993,10 @@ document.write("Last Published: " + docu
<br>
<br>
<p>Enter a desired access token, and click the "Add" button. You may enter multiple access tokens.</p>
-<a name="N10B3E"></a><a name="filenetrepository"></a>
+<a name="N10B5A"></a><a name="filenetrepository"></a>
<h3 class="h4">IBM FileNet P8 Repository Connection</h3>
<p>More here later</p>
-<a name="N10B48"></a><a name="documentumrepository"></a>
+<a name="N10B64"></a><a name="documentumrepository"></a>
<h3 class="h4">EMC Documentum Repository Connection</h3>
<p>The EMC Documentum connection type allows you index content from a Documentum Content Server instance. A single connection allows you
to reach all documents contained on a single Content Server instance. Multiple connections are therefore required to reach documents from multiple Content Server instances.</p>
@@ -2034,7 +2051,7 @@ document.write("Last Published: " + docu
<p>For example, suppose you had a rule which had ".*/(.*)/(.*)/.*" as a match expression, and "$(1) $(2)" as the replace string. If presented with the path
<span class="codefrag">Project/Folder_1/Folder_2/Filename</span>, it would output the string <span class="codefrag">Folder_1 Folder_2</span>.</p>
<p>If more than one rule is present, the rules are all executed in sequence. That is, the output of the first rule is modified by the second rule, etc.</p>
-<a name="N10BAE"></a><a name="livelinkrepository"></a>
+<a name="N10BCA"></a><a name="livelinkrepository"></a>
<h3 class="h4">OpenText LiveLink Repository Connection</h3>
<p>The OpenText LiveLink connection type allows you to index content from LiveLink repositories. LiveLink has a rich variety of different document types and metadata, which include
basic documents, as well as compound documents, folders, workspaces, and projects. A LiveLink connection is able to discover documents contained within all of these constructs.</p>
@@ -2129,7 +2146,7 @@ document.write("Last Published: " + docu
<p>For example, suppose you had a rule which had ".*/(.*)/(.*)/.*" as a match expression, and "$(1) $(2)" as the replace string. If presented with the path
<span class="codefrag">Project/Folder_1/Folder_2/Filename</span>, it would output the string <span class="codefrag">Folder_1 Folder_2</span>.</p>
<p>If more than one rule is present, the rules are all executed in sequence. That is, the output of the first rule is modified by the second rule, etc.</p>
-<a name="N10C5D"></a><a name="mexexrepository"></a>
+<a name="N10C79"></a><a name="mexexrepository"></a>
<h3 class="h4">Memex Patriarch Repository Connection</h3>
<p>A Memex Patriarch connection allows you to index documents from a Memex server.</p>
<p>Documents described by Memex connections are typically secured by a Memex authority. If you have not yet created a Memex authority, but would like your
@@ -2163,7 +2180,7 @@ document.write("Last Published: " + docu
<p></p>
<p>Jobs based on Memex connections have the following special tabs: "Record Criteria", "Entities", and "Security".</p>
<p>More here later</p>
-<a name="N10CA2"></a><a name="meridiorepository"></a>
+<a name="N10CBE"></a><a name="meridiorepository"></a>
<h3 class="h4">Autonomy Meridio Repository Connection</h3>
<p>An Autonomy Meridio connection allows you to index documents from a set of Meridio servers. Meridio's architecture allows you to separate services on multiple machines -
e.g. the document services can run on one machine, and the records services can run on another. A Meridio connection type correspondingly is configured to describe each
@@ -2237,7 +2254,7 @@ document.write("Last Published: " + docu
<p></p>
<p>Jobs based on Meridio connections have the following special tabs: "Search Paths", "Content Types", "Categories", "Data Types", "Security", and "Metadata".</p>
<p>More here later</p>
-<a name="N10D28"></a><a name="sharepointrepository"></a>
+<a name="N10D44"></a><a name="sharepointrepository"></a>
<h3 class="h4">Microsoft SharePoint Repository Connection</h3>
<p>The Microsoft SharePoint connection type allows you to index documents from a Microsoft SharePoint site. Bear in mind that a single SharePoint installation actually represents
a set of sites. Some sites
Modified: incubator/lcf/site/publish/end-user-documentation.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/end-user-documentation.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Files incubator/lcf/site/publish/end-user-documentation.pdf (original) and incubator/lcf/site/publish/end-user-documentation.pdf Thu Jul 8 15:01:08 2010 differ
Modified: incubator/lcf/site/publish/faq.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/faq.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Files incubator/lcf/site/publish/faq.pdf (original) and incubator/lcf/site/publish/faq.pdf Thu Jul 8 15:01:08 2010 differ
Modified: incubator/lcf/site/publish/images/solr-configure-arguments.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/solr-configure-arguments.PNG?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Added: incubator/lcf/site/publish/images/solr-configure-schema.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/solr-configure-schema.PNG?rev=961792&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/lcf/site/publish/images/solr-configure-schema.PNG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/lcf/site/publish/images/solr-configure-server.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/solr-configure-server.PNG?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Added: incubator/lcf/site/publish/images/solr-job-field-mapping.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/solr-job-field-mapping.PNG?rev=961792&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/lcf/site/publish/images/solr-job-field-mapping.PNG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/lcf/site/publish/images/solr-status.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/solr-status.PNG?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/index.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/index.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/linkmap.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/linkmap.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/mail.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/mail.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/who.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/who.pdf?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
--- incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml (original)
+++ incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml Thu Jul 8 15:01:08 2010
@@ -420,13 +420,18 @@
<p>Unfortunately, this lack of specificity comes at a cost. Unless you take care to filter documents properly in each job, large movie files or other opaque
content may well be picked up and sent to Solr for indexing, which will greatly increase the dead load on the overall system. It is therefore a good idea to review
all crawls done through a Solr connection while they are underway, to be sure there isn't a misconfiguration of this kind.</p>
- <p>When you create a Solr output connection, two configuration tabs appear. The "Server" tab allows you to configure the HTTP target of the connection:</p>
+ <p>When you create a Solr output connection, three configuration tabs appear. The "Server" tab allows you to configure the HTTP target of the connection:</p>
<br/><br/>
<figure src="images/solr-configure-server.PNG" alt="Solr Configuration, Server tab" width="80%"/>
<br/><br/>
<p>Fill in the fields according to your Solr configuration. The Solr connection type supports only basic authentication at this time; if you have this enabled, supply the credentials
as requested on the bottom part of the form.</p>
- <p>The second tab is the "Arguments" tab, which allows you to specify arbitrary arguments to be sent to Solr. This is a popular way of telling Solr how to handle
+ <p>The second tab is the "Schema" tab, which allows you to specify the name of the Solr field to use as a document identifier. The Solr connection type will treat
+ this field as being a unique key for locating the indexed document for further modification or deletion:</p>
+ <br/><br/>
+ <figure src="images/solr-configure-schema.PNG" alt="Solr Configuration, Schema tab" width="80%"/>
+ <br/><br/>
+ <p>The third tab is the "Arguments" tab, which allows you to specify arbitrary arguments to be sent to Solr. This is a popular way of telling Solr how to handle
specific documents, so the connection type allows you to add arguments to each Solr indexing request:</p>
<br/><br/>
<figure src="images/solr-configure-arguments.PNG" alt="Solr Configuration, Arguments tab" width="80%"/>
@@ -439,9 +444,15 @@
<figure src="images/solr-status.PNG" alt="Solr Status" width="80%"/>
<br/><br/>
<p>Note that in this example, the Solr connection is not responding, which is leading to an error status message instead of "Connection working".</p>
- <p>When you configure a job to use a Solr-type output connection, no Solr-specific additional tabs appear at this time. In the future, this may well change, and job-specific
- tabs could be added, most likely to allow job-specific arguments to be added to each index request. If functionality of this kind seems important to your application,
- please do not hesitate to contact the Lucene Connectors Framework team with your request.</p>
+ <p>When you configure a job to use a Solr-type output connection, the Solr connection type provides a tab called "Field Mapping". The purpose of this tab
+ is to allow you to map metadata fields as fetched by the job's connection type to fields that Solr is set up to receive. This is necessary because
+ the names of the metadata items are often determined by the repository, with no alignment to fields defined in the Solr schema. You may also
+ suppress specific metadata items from being sent to the index using this tab. The tab looks like this:</p>
+ <br/><br/>
+ <figure src="images/solr-job-field-mapping.PNG" alt="Solr Specification, Field Mapping tab" width="80%"/>
+ <br/><br/>
+ <p>Add a new mapping by filling in the "source" with the name of the metadata item from the repository, and "target" as the name of the output field in
+ Solr, and click the "Add" button. Leaving the "target" field blank will result in all metadata items of that name not being sent to Solr.</p>
</section>
<section id="gtsoutputconnector">
Modified: incubator/lcf/site/src/documentation/resources/images/solr-configure-arguments.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/solr-configure-arguments.PNG?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Added: incubator/lcf/site/src/documentation/resources/images/solr-configure-schema.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/solr-configure-schema.PNG?rev=961792&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/lcf/site/src/documentation/resources/images/solr-configure-schema.PNG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/lcf/site/src/documentation/resources/images/solr-configure-server.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/solr-configure-server.PNG?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.
Added: incubator/lcf/site/src/documentation/resources/images/solr-job-field-mapping.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/solr-job-field-mapping.PNG?rev=961792&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/lcf/site/src/documentation/resources/images/solr-job-field-mapping.PNG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/lcf/site/src/documentation/resources/images/solr-status.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/solr-status.PNG?rev=961792&r1=961791&r2=961792&view=diff
==============================================================================
Binary files - no diff available.