That should be a small change (and helpful for a lot of mining tasks). But once you jump on that slippery slope, why not allow a tiny Groovy closure to be injected? Or to pass in an object that will extract a map of values from each line?
On Thu, May 27, 2010 at 2:59 PM, Grant Ingersoll <[email protected]>wrote: > Actually, I take it back, as it is not what I want. > > Given a line like: > 127.0.0.1 - - [24/05/2010:01:19:22 +0000] "GET /solr/select?q=import > statement&start=1(MORE HERE) HTTP/1.1" 200 37571 > > I want to be able to grab the q parameter (ie. "import statement") and put > that as my item for that document. It needs to split the value within &q as > well, so it should be "import" and "statement". > > I guess I was proposing that instead of splitting on the parameter, I would > be only including those items that match a capturing group (all by default, > but also optionally passed in) >
