lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "DataImportHandler" by FergusMcMenemie
Date Tue, 06 Oct 2009 09:55:34 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "DataImportHandler" page has been changed by FergusMcMenemie:
http://wiki.apache.org/solr/DataImportHandler?action=diff&rev1=213&rev2=214

      <document>
          <entity name="f" processor="FileListEntityProcessor" baseDir="/some/path/to/files"
fileName=".*xml" newerThan="'NOW-3DAYS'" recursive="true" rootEntity="false" dataSource="null">
              <entity name="x" processor="XPathEntityProcessor" forEach="/the/record/xpath"
url="${f.fileAbsolutePath}">
+                 <field column source]]
+ 
-                 <field column="full_name" xpat0Aand can be used as a !DataSource. It
must be3A//abc.com/a.txt" dataSource="data-source-name">
+ and can be used as a !DataSource. It must be3A//abc.com/a.txt" dataSource="data-source-name">
     <!-- copies the text to a field called 'text' in Solr-->
    <field column="plainText" name="text"/>
  </entity>
@@ -872, +874 @@

  }}}
  
  === HttpDataSource ===
- <!> Http!DataSource is being deprecated in favour of URL!DataSource in [[Solr1.4]].
There is no change in functionality between URL!DataSource and !Http!DataSource, only a name
change.
+ <!> Http!DataSource is being deprecated in favour of URLDataSource in [[Solr1.4]].
There is no change in functionality between URLDataSource and !Http!DataSource, only a name
change.
  
  === FileDataSource ===
  This can be used like an URL!DataSource but used to fetch content from files on disk. The
only difference from URL!DataSource, when accessing disk files, is how a pathname is specified.
The signature is as follows
@@ -887, +889 @@

  === FieldReaderDataSource ===
  <!> [[Solr1.4]]
  
- This can be used like an URL!DataSource . The signature is as follows
+ This can be used like an URLDataSource. But instead of reading from a file:// or http://
location the entity parses the contents of a field fetched by another !EntityProcessor. For
instance an outer !EntityProcessor could be fetching fields from a DB where one of the fields
contains XML. The field containing XML could be processed by an inner XPathEntityProcessor.
 The signature is as follows
  {{{
  public class FieldReaderDataSource extends DataSource<Reader>
  }}}
- This can be useful for users who have a DB field containing XML and wish to use a nested
X!PathEntityProcessor to process the fields contents.
+ This can be useful for users who have a DB field containing XML and wish to use a nested
XPathEntityProcessor to process the fields contents.
  The datasouce may be configured as follows
  {{{
    <datasource name="f" type="FieldReaderDataSource" />
  }}}
  
- The enity which uses this datasource must keep the url value as the variable name dataField="field-name".
For instance , if the parent entity 'dbEntity' has a field called 'xmlData' . Then he child
entity woould look like,
+ The entity which uses this datasource must specify the variable using the name dataField="field-name".
For instance, if the parent entity 'dbEntity' has a field called 'xmlData'. Then he child
entity would look like,
  {{{
  <entity dataSource="f" processor="XPathEntityProcessor" dataField="dbEntity.xmlData"/>
  }}}

Mime
View raw message