On Mon, Feb 2, 2009 at 9:20 PM, Jon Baer <jonb...@gmail.com> wrote: > Hi, > > Sorry I know this exists ... > > "If an API supports chunking (when the dataset is too large) multiple calls > need to be made to complete the process. XPathEntityprocessor supports this > with a transformer. If transformer returns a row which contains a field * > $hasMore* with a the value "true" the Processor makes another request with > the same url template (The actual value is recomputed before invoking ). A > transformer can pass a totally new url too for the next call by returning a > row which contains a field *$nextUrl* whose value must be the complete url > for the next call." > > But is there a true example of it's use somewhere? Im trying to figure out > if I know before import that I have 56 "pages" to index how to set this up > properly. (And how to set it up if pages need to be determined by > something > in the feed, etc). >
No, there is no example (yet). You'll put the url with variables for the corresponding 'start' and 'count' parameters and a custom transformer can specify if another request needs to be made. I know it's not much to go on. I'll try to write some documentation on the wiki. SOLR-994 might be interesting to you. I haven't been able to look at the patch though. https://issues.apache.org/jira/browse/SOLR-994 -- Regards, Shalin Shekhar Mangar.
