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 JamesDyer:
http://wiki.apache.org/solr/DataImportHandler?action=diff&rev1=313&rev2=314
Comment:
More information about 'threads' parameter, fixed some hyperlinks
* '''`transformer`''' : Transformers to be applied on this entity. (See the transformer
section)
* '''`dataSource`''' : The name of a datasource as put in the the datasource .(Used if
there are multiple datasources)
* '''`threads`''' : The no:of of threads to use to run this entity. This must be placed
on or above a 'rootEntity'. [[Solr3.1]]
+ * Warning: Not all combinations of DIH components can be used safely with 'threads'.
If using this feature, be sure to test thoroughly!
+ * Significant bugs related to 'threads' are fixed with [[Solr3.6]]. If using this feature
with an older version, upgrading is recommended. See [[https://issues.apache.org/jira/browse/SOLR-3011|SOLR-3011]]
+ * The 'threads' parameter is Deprecated as of [[Solr3.6]] and is slated for removal in
[[Solr4.0]]. [[https://issues.apache.org/jira/browse/SOLR-3262|SOLR-3262]]
* '''`pk`''' : The primary key for the entity. It is '''optional''' and only needed when
using delta-imports. It has no relation to the uniqueKey defined in schema.xml but they both
can be the same.
* '''`rootEntity`''' : By default the entities falling under the document are root entities.
If it is set to false , the entity directly falling under that entity will be treated as the
root entity (so on and so forth). For every row returned by the root entity a document is
created in Solr
* '''`onError`''' : (abort|skip|continue) . The default value is 'abort' . 'skip' skips
the current document. 'continue' continues as if the error did not happen . <!> [[Solr1.4]]
@@ -844, +847 @@
In the where the lhs (the part before '=') is the column in y and the rhs (the part after
'=') is the value to be computed for looking up the cache.
----
- For more caching options with DIH see https://issues.apache.org/jira/browse/SOLR-2382.
These additional options include: using caches with non-sql entities, pluggable cache implementations,
persistent caches, writing DIH output to a cache rather than directly to solr, using a previously-created
cache as a DIH entity's input & delta updates on cached data.
+ For more caching options with DIH see [[https://issues.apache.org/jira/browse/SOLR-2382|SOLR-2382]].
These additional options include: using caches with non-sql entities, pluggable cache implementations,
persistent caches, writing DIH output to a cache rather than directly to solr, using a previously-created
cache as a DIH entity's input & delta updates on cached data. Some of these features
are currently available [[Solr3.6]] [[Solr4.0]]
----
=== PlainTextEntityProcessor ===
@@ -890, +893 @@
While there are use cases where you might need to create a solr document per line read from
a file, it is expected that in most cases that the lines read will consist of a pathname which
is in turn consumed by another !EntityProcessor such as XPathEntityProcessor.
----
- See https://issues.apache.org/jira/browse/SOLR-2549 for a patch that extends LineEntityProcessor
to support fixed-width and delimited files without needing to use a Transformer.
+ See [[https://issues.apache.org/jira/browse/SOLR-2549|SOLR-2549]] for a patch that extends
LineEntityProcessor to support fixed-width and delimited files without needing to use a Transformer.
----
=== SolrEntityProcessor ===
@@ -996, +999 @@
* '''`$deleteDocById`''' : Delete a doc from Solr with this id. The value has to be the
uniqueKey value of the document. Note that this command can only delete docs already committed
to the index. <!> [[Solr1.4]]
* '''`$deleteDocByQuery`''' :Delete docs from Solr by this query. The value must be a Solr
Query <!> [[Solr1.4]]
- Note: prior to Solr 3.4, $deleteDocById and $deleteDocByQuery do not increment the "# deletes
processed" statistic. Also, if a component ''only'' deletes documents using these special
commands, DIH will not commit the changes. With Solr 3.4 and later, "commit" is always called
as expected and the "# deletes processed" statistic is incremented by 1 for each call to $deleteDocById
and/or $deleteDocByQuery. This may not accurately reflect the actual number of documents
deleted as these commands (especially $deleteDocByQuery) can delete more than 1 document (or
no documents) per call. See https://issues.apache.org/jira/browse/SOLR-2492 for a more information.
+ Note: prior to Solr 3.4, $deleteDocById and $deleteDocByQuery do not increment the "# deletes
processed" statistic. Also, if a component ''only'' deletes documents using these special
commands, DIH will not commit the changes. With Solr 3.4 and later, "commit" is always called
as expected and the "# deletes processed" statistic is incremented by 1 for each call to $deleteDocById
and/or $deleteDocByQuery. This may not accurately reflect the actual number of documents
deleted as these commands (especially $deleteDocByQuery) can delete more than 1 document (or
no documents) per call. See [[https://issues.apache.org/jira/browse/SOLR-2492|SOLR-2492]]
for a more information.
== Adding datasource in solrconfig.xml ==
<<Anchor(solrconfigdatasource)>>
|