No, you do not have to store anything for copyField to work. You're overthinking the problem.
Way up top, when the original data comes in to a field (indexed or not, stored or not) the schema is scanned for any copyfields that use the field for a source. Then the whole input is sent to both fields, exactly as if you added two fields separately to the document. Please just try it, it'll short-circuit a ton of e-mails... Best Erick On Tue, Sep 18, 2012 at 7:21 AM, Spadez <james_will...@hotmail.com> wrote: > Ok, I’ve been doing a bit more research. In order to do the copyfield > technique, I need to store the original full text document within Solr, like > this: > > <field name="truncated_description" indexed="false" stored="false"> > <field name="keyword_description" indexed="true" > stored="<b>true*"> > > What about instead if I imported the same fulltext into two seperate fields > for Solr by my Python script: > > trucated_description=post.description, > keyword_description=post.description, > > Doing it this way, I wouldnt need to store the fulltext in Solr, so I could > do this: > <field name="truncated_description" indexed="false" > stored="<b>false*"> > <field name="keyword_description" indexed="true" > stored="<b>false*"> > > I'm still learning about this, but by importing it twice, I think remove the > need to ever store the uneccessary fulltext document in its original form > within Solr > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Taking-a-full-text-then-truncate-and-duplicate-with-stopwords-tp4008269p4008580.html > Sent from the Solr - User mailing list archive at Nabble.com.
