you can share the details on how you were identifying deltas and what are the methods you would like to make protected.
delta import necessarily does not need the entityprocessor to support it. you can easily do delta-import with a full-import . http://wiki.apache.org/solr/DataImportHandlerFaq#head-0d5144d35dfdba4ba9e182a46ed71c15c3b5a1c6 On Wed, Feb 25, 2009 at 8:02 PM, Benjamin Liles <bli...@library.tamu.edu> wrote: > I was looking at adding support to the XPathEntityProcessor for a > DeltaImport by adding a new parameter, deltaUrl, in order to support > harvesting from an OAI-PMH server into SOLR. I wasn't planning on bothering > with getting commit access to the repository so I was looking to extend the > XPathEntityProcessor in my own package. I ran into a problem because most > of the methods on the class are private instead of protected. I only want to > override a methods and not all of them. > > Should I just modify the XPathEntityProcessor to add the functionality and > submit a patch instead of trying to write my own class that extends the > XPathEntityProcessor? > > Was there a reason for making the methods be private? > > Benjamin Liles > Lead Software App Developer > Texas A&M University General Libraries > PH 979.862.4948 ex 122 > bli...@library.tamu.edu > > -- --Noble Paul
