[
https://issues.apache.org/jira/browse/NUTCH-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677261#action_12677261
]
Gopikrishnan commented on NUTCH-185:
------------------------------------
Building XMLParser plugin with the latest (1.0-dev) source, throw errors for
the following classes because of changes in base interfaces
org\apache\nutch\parse\xml\config\XMLIndexer.java :
org\apache\nutch\parse\xml\XMLIndexer.java:40:
org.apache.nutch.parse.xml.XMLIndexer is not abstract and does not override
abstract method
addIndexBackendOptions(org.apache.hadoop.conf.Configuration) in
org.apache.nutch.indexer.IndexingFilter
org\apache\nutch\parse\xml\XMLParser.java :
org\apache\nutch\parse\xml\XMLParser.java:64:
org.apache.nutch.parse.xml.XMLParser is not abstract and does not override
abstract method getParse(org.apache.nutch.protocol.Content)
in org.apache.nutch.parse.Parser
org\apache\nutch\parse\xml\XMLParser.java:75:
getParse(org.apache.nutch.protocol.Content) in
org.apache.nutch.parse.xml.XMLParser cannot implement
getParse(org.apache.nutch.protocol.Content) in org.apache.nutch.parse.Parser;
attempting to use incompatible return type
Could somebody tell me what are the changes to make this plugin compatible with
the Nutch trunk (1.0)
> XMLParser is configurable xml parser plugin.
> --------------------------------------------
>
> Key: NUTCH-185
> URL: https://issues.apache.org/jira/browse/NUTCH-185
> Project: Nutch
> Issue Type: New Feature
> Components: fetcher, indexer
> Affects Versions: 0.7.2, 0.8, 0.8.1
> Environment: OS Independent
> Reporter: Rida Benjelloun
> Assignee: Chris A. Mattmann
> Attachments: parse-xml.patch, parse-xml.zip, parse-xml.zip
>
>
> Xml parser is configurable plugin. It use XPath and namespaces to do the
> mapping between the XML elements and Lucene fields.
> Informations :
> 1- Copy "xmlparser-conf.xml" to the nutch/conf dir
> 2- To index your custom XML file, you have to modify the
> "xmlparser-conf.xml".
> This parser uses namespaces and XPATH to parse XML content
> The config file do the mapping between the XML noeds (using XPATH) and lucene
> field.
> Example : <field name="dctitle" xpath="//dc:title" type="Text" boost="1.4" />
> 3- The xmlIndexerProperties encapsulate a set of fields associated to a
> namespace.
> If the namespace is found in the xml document, the fields represented by the
> namespace will be indexed.
> Example :
> <xmlIndexerProperties type="filePerDocument" namespace="
> http://purl.org/dc/elements/1.1/";>
> <field name="dctitle" xpath="//dc:title" type="Text" boost=" 1.4" />
> <field name="dccreator" xpath="//dc:creator" type="keyword" boost=" 1.0" />
> </xmlIndexerProperties>
> 4- It is possible to define a default namespace that will be applied when the
> parser
> didn't find any namespace in the document or when the namespace found in the
> xml document doesn't match with the namespace defined in the
> xmlIndexerProperties.
> Example :
> <xmlIndexerProperties type="filePerDocument" namespace="default">
> <field name="xmlcontent" xpath="//*" type="Unstored" boost="1.0" />
> </xmlIndexerProperties>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
