Re: Updating and Appending

2008-01-24 Thread Jeff Rodenburg
On Jan 23, 2008 1:29 PM, Chris Harris [EMAIL PROTECTED] wrote: And then if you're using a client such as solrsharp, there's the question of whether *it* will slurp the whole stream into memory. Solrsharp reads of the XML stream from Solr use standard dotnet framework XML objects, which by

Re: Updating and Appending

2008-01-23 Thread Yonik Seeley
On Jan 22, 2008 4:10 PM, Owens, Martin [EMAIL PROTECTED] wrote: We've got some memory constraint worries from using Java RMI, although I can see this problem could effect the xml requests too. The Java code doesn't seem to handle large files as streams. It depends on what component we are

Re: Updating and Appending

2008-01-23 Thread Chris Harris
On Jan 23, 2008 9:04 AM, Yonik Seeley [EMAIL PROTECTED] wrote: On Jan 22, 2008 4:10 PM, Owens, Martin [EMAIL PROTECTED] wrote: We've got some memory constraint worries from using Java RMI, although I can see this problem could effect the xml requests too. The Java code doesn't seem to

Re: Updating and Appending

2008-01-23 Thread Yonik Seeley
On Jan 23, 2008 4:29 PM, Chris Harris [EMAIL PROTECTED] wrote: Supposing you could do this -- i.e. that you could get Solr to pass a particular field's data to Lucene without reading it all into memory first --, are there any potential problems on the Lucene end? It's not going to turn around

Updating and Appending

2008-01-22 Thread Owens, Martin
Hello, We've got some memory constraint worries from using Java RMI, although I can see this problem could effect the xml requests too. The Java code doesn't seem to handle large files as streams. Now we're thinking that there are two possible solutions, either the exists or we create a file