: > Right, you're getting at issues of why I haven't committed my CSV handler yet. : > It currently handles reading a local file (this is more like an SQL : > update handler... only a reference to the data is passed). But I also : > wanted to be able to handle a POST of the data , or even a file : > upload from a browser. Then I realized that this should be generic... : > the same should also apply to XML updates, and potential future update : > formats like JSON. : : I do not see the problem here. One just need to add a couple of lines in : the upload servlet and change the csv plugin to input stream (not local : file).
what Yonik and i are worried about is that we don't want the list of all possible ways for an Update Plugin to get a Stream to be hardcoded in the UpdateServlet or Solr Core or in the Plugins themselves ... we'd like the notion of indexing docs expressed as CSV records or XML records or JSON records to be independent of where the CSV, XML, or JSON data stream came from ... in the same way that the current RequestHandlers can execute specific search logic, without needing to worry about what format the results are going to be returned in. It's not writting code to get the stream from one of N known ways that's hard -- it's designing an API so we can get the stream from one of any number of *unknown* ways that can be specified at run time thats tricky :) -Hoss
