The case changed to not using those xml-files at all, i ended up using
some other datafiles as sources, witch had everything flat, so no
recursion was needed afterall. But thanks for the input! :)
Best regards
On Tue, Jun 8, 2010 at 11:08 AM, Geert-Jan Brits wrote:
> my bad, it looks like XPathE
my bad, it looks like XPathEntityProcessor doesn't support relative xpaths.
However, I quickly looked at the Slashdot example (which is pretty good
actually) at http://wiki.apache.org/solr/DataImportHandler.
>From that I infer that you use only 1 entity per xml-doc. And within that
entity use mult
I have tried both to change the datasource per child node to use the
parent nodes name, and tried to making the Xpath`s relative, all
causing either exceptions telling that Xpath must start with /, or
nullpointer exceptions ( nsfgrantsdir document : null).
Best regards
On Mon, Jun 7, 2010 at 4:12
I'm guessing (I'm not familiar with the xml dataimport handler, but I am
pretty familiar with Xpath)
that your problem lies in having absolute xpath-queries, instead of relative
xpath queries to your parent node.
e.g: /DOK/TEKST/KAP is absolute ( the prefixed '/' tells it to be). Try
'KAP' instead
Hi,
I am doing some testing of dataimport to Solr from XML-documents with
many children in the children. To parse the children i some levels
down using Xpath goes fine, but the speed is very slow. (~1 minute per
document, on a quad Xeon server). When i do the same using the format
solr wants it, t
