Re: schema question

Yeah, probably the SignatureUpdateProcessorFactory can do the trick, but you still need to write a custom Signature. (we should really offer a simple "ConcatSignature" implementation for generating predictable combination keys) +1 Cheers, Uri Chris Hostetter wrote: : TemplateTranformer. Other

Re: schema question

: TemplateTranformer. Otherwise, if you really must do it in Solr you can write : your own custom UpdateProcessor and plug it in: Can't the SignatureUpdateProcessorFactory handle this using something like Lookup3Signature? (we should really offer a simple "ConcatSignature" implementation for g

Re: schema question

Using copyField will add three different values to the unique id field; it will not concatenate them into one value. It has to be a single-valued field. The three values have to be concatenated in DIH or in the feeding application. On Sun, Jan 17, 2010 at 6:41 PM, William Bell wrote: > You could

Re: schema question

You could use a copyField. On 1/17/10 1:47 PM, "Koji Sekiguchi" wrote: > Pradeep Pujari wrote: >> how can I specify uniqueKey value in schema.xml as a concatenation of 3 >> columns. Like prod_id+attr_name+att_value? >> >> Thanks, >> Pradeep >> >> > Solr doesn't support it. You should conca

Re: schema question

If you're using DataImportHandler than this can easily be done with a TemplateTranformer. Otherwise, if you really must do it in Solr you can write your own custom UpdateProcessor and plug it in: DIH TemplateTransformer: http://wiki.apache.org/solr/DataImportHandler#TemplateTransformer Update

Re: schema question

Pradeep Pujari wrote: how can I specify uniqueKey value in schema.xml as a concatenation of 3 columns. Like prod_id+attr_name+att_value? Thanks, Pradeep Solr doesn't support it. You should concatenate them at client. Koji -- http://www.rondhuit.com/en/

Re: Schema question: overriding fieldType attributes in field element

: Unfortunately, unless I've missed something obvious, the "tokenized" : property is not available to classes that extend FieldType: the setArgs() : method of FieldType strips "tokenized" and other standard properties away : before calling the init() method. Yes, of course one could override : set

Re: Schema question: overriding fieldType attributes in field element

Chris Hostetter <[EMAIL PROTECTED]> wrote on 05/31/2007 02:28:58 PM: > I'm having a little trouble following this discussion, first off as to > your immediate issue... > > : Thanks, but I think I'm going to have to work out a different solution. I > : have written my own analyzer that does ever

Re: Schema question: overriding fieldType attributes in field element

On 5/31/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: ...maybe there is some terminology confusion here I think the issue is the additional restrictions: "consolidate all field properties to the field element. The reason for this is that the schema is read by another class to give access to f

Re: Schema question: overriding fieldType attributes in field element

I'm having a little trouble following this discussion, first off as to your immediate issue... : Thanks, but I think I'm going to have to work out a different solution. I : have written my own analyzer that does everything I need: it's not a : different analyzer I need but a way to specify that

Re: Schema question: overriding fieldType attributes in field element

On 31-May-07, at 8:47 AM, [EMAIL PROTECTED] wrote: Thanks, but I think I'm going to have to work out a different solution. I have written my own analyzer that does everything I need: it's not a different analyzer I need but a way to specify that certain fields should be tokenized and others

Re: Schema question: overriding fieldType attributes in field element

Thanks, but I think I'm going to have to work out a different solution. I have written my own analyzer that does everything I need: it's not a different analyzer I need but a way to specify that certain fields should be tokenized and others not -- while still leaving all other options open. As

Re: Schema question: overriding fieldType attributes in field element

On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: You say the "tokenized" attribute is not settable from the schema, but the output from IndexSchema.readConfig shows that the properties are indeed read, and the resulting SchemaField object retains these properties: are they then ignored?

Re: Schema question: overriding fieldType attributes in field element

Thanks for the prompt response. Comments below ... [EMAIL PROTECTED] wrote on 05/31/2007 10:55:57 AM: > On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I am trying to override the tokenized attribute of a single FieldType from > > the field attribute in schema.xml, but it doesn't se

Re: Schema question: overriding fieldType attributes in field element

On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I am trying to override the tokenized attribute of a single FieldType from the field attribute in schema.xml, but it doesn't seem to work The "tokenized" attribute is not settable from the schema, and there is no reason I can think of why