On Jan 8, 2008 12:59 PM, Michael Lackhoff <[EMAIL PROTECTED]> wrote: > On 08.01.2008 16:55 Yonik Seeley wrote: > > >> - A literal encapsulator should be possible to add by doubling > >> it ' => '' but this gives the same error > > > > I think you would have to tripple it (the first is the encapsulator). > > Regardless, don't use encapsulation on the split fields unless you > > have to. > > I don't want to use encapsulation it is just that the character is > _interpreted_ as encapsulation character and I need a way to tell SOLR > that it is not.
I understand... I meant that the easiest way to avoid having that character interpreted as encapsulation is to turn off encapsulation (by setting it to a char that won't ever match). The harder way is to escape the encapsulator... per standard CSV, that requires first encapsulating the field value and then doubling the encapsulation char where it appears in the value. So 'a would be '''a' (three single quotes to start the value). > >> - is it possible to change the split field separator for all fields? The > >> URL is getting rather long already. > > > > if "f.myfield.separator" is missing, it uses "separator" (standard > > per-field parameters). > > So if everything uses "," you don't have to specify a separator anywhere. > > Oh, sorry, I meant encapsulator of course, not separator. The > encapsulator is the problem and I would like a way shorter than > &f.myfield1.encapsultor=%00&f.myfield2.encapsulator=%00... for about 20 > fields in addition to the parameters that are necessary to tell SOLR > that all these are split fields. There is no shorter way, but if you update to the latest solr-dev (changes I checked in today), the default will be no encapsulation for split fields. -Yonik
