We are cutting a a patch which incorporates all the recent bug fixes,
so that you guys do not have to apply patches over patches
--Noble
On Wed, Jun 11, 2008 at 3:49 PM, Nicolas Pastorino <[EMAIL PROTECTED]> wrote:
> Thanks a million for your time and help.
> It indeed works smoothly now.
>
> I a
Thanks a million for your time and help.
It indeed works smoothly now.
I also, by the way, had to apply the "patch" attached to the
following message :
http://www.nabble.com/Re%3A-How-to-describe-2-entities-in-dataConfig-
for-the-DataImporter--p17577610.html
in order to have the TemplateTransf
It is a bug, nice catch
there needs to be a null check there in the method
can us just try replacing the method with the following?
private Node getMatchingChild(XMLStreamReader parser) {
if(childNodes == null) return null;
String localName = parser.getLocalName();
for (Node n :
I just forgot to mention the error related to the description below.
I get the following when running a full-import ( sorry for the
noise .. ) :
SEVERE: Full Import failed
java.lang.RuntimeException: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.XPathRecordRea
Thanks a lot, it works fine now, fetching subelements properly.
The only issue left is that the XPath syntax passed in the data-
config.xml does not seem to work properly. As an example, processing
the following entity :
This is my title
The configuration is fine but for one detail
The documents are to be created for the entity 'oldsearchcontent' not
for the root entity . so add an attribute rootEntity="false" for the
entity 'oldsearchcontentlist' as follows.
http://localhost/psc/trunk/ezfiles/list_old_content.php?limit=10&urls
Hello fellow Solr users !
I am in the process of trying to index XML documents in Solr. I went
for the DataImportHandler approach, which seemed to perfectly suit
this need. Due to the large amount of XML documents to be indexed
( ~60MB ), i thought i would hardly be possible to feed solr w
