lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Wolanin (JIRA)" <>
Subject [jira] Updated: (SOLR-2149) Allow copyField directives to be controled by another (boolean) field
Date Sun, 10 Oct 2010 14:57:30 GMT


Peter Wolanin updated SOLR-2149:

    Attachment: SOLR-2149.patch

The attached patch against 1.4 is not at all functional, just taking a rough look at where
the code would need to be modified.

> Allow copyField directives to be controled by another (boolean) field
> ---------------------------------------------------------------------
>                 Key: SOLR-2149
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Peter Wolanin
>         Attachments: SOLR-2149.patch
> Thinking about alternative approaches to the problem outlined in SOLR-2010, it occurs
to me that there are many cases where it would be useful to be able to control copyField behavior
rather than having to fully populate or omit document fields.  In regards to spellcheck, I
could then have a few different spellcheck indexes each built from a different field  and
indicate for each document whether it's text should be added to each of the different spellcheck
> I'm imagining a general syntax like this:
> {code}
>  <copyField source="body" dest="teaser" maxChars="300" controlField="populate_teaser"/>
> {code}
> If not sure if Solr would could use the value of a control field only matches the "ignored"
field type, but that's what I'm thinking about as one possibility.  In other words, I can
pass index-time flags into the document that are reflected in the terms of what's indexed
but not explicitly stored in the document.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message