urce text is "stored".
-- Jack Krupansky
-Original Message-
From: Spadez
Sent: Tuesday, September 18, 2012 10:33 AM
To: solr-user@lucene.apache.org
Subject: Re: Taking a full text, then truncate and duplicate with stopwords
Ok, thank you for the reply. I have one more question then I th
Ok, thank you for the reply. I have one more question then I think everything
is cleared up. If I have this code:
The truncated_description is one I need to display in search results. If I
set this to stored=true as above (so it can be displayed in results), does
it mean that I am storing t
ssage-
From: Spadez
Sent: Tuesday, September 18, 2012 7:21 AM
To: solr-user@lucene.apache.org
Subject: Re: Taking a full text, then truncate and duplicate with stopwords
Ok, I’ve been doing a bit more research. In order to do the copyfield
technique, I need to store the original full te
Hi James,
> In order to do the copyfield
> technique, I need to store the original full text document
> within Solr, like
> this:
>
> stored="false">
> indexed="true"
> stored="true*">
No, that's not true. You can use copyField with stored="false". In other words,
source field ( keyword_d
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
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:
true*">
What about instead if I imported the same fulltext into two seperate fields
for Solr by my Python script:
trucated_description=post.d
012 4:47 PM
To: solr-user@lucene.apache.org
Subject: Re: Taking a full text, then truncate and duplicate with stopwords
Ah, ok this is news to me and makes a lot more sense. If I can just run this
back past you to make sure I understand. If I move my full_text to
If I move my fulltext documen
;
> -- Jack Krupansky
>
> -Original Message-
> From: Spadez
> Sent: Monday, September 17, 2012 12:29 PM
> To: solr-user@.apache
> Subject: Re: Taking a full text, then truncate and duplicate with
> stopwords
>
> I'm really confused here. I have a docu
index the value in
different ways.
-- Jack Krupansky
-Original Message-
From: Spadez
Sent: Monday, September 17, 2012 12:29 PM
To: solr-user@lucene.apache.org
Subject: Re: Taking a full text, then truncate and duplicate with stopwords
I'm really confused here. I have a document wh
> Then if I do copy command to move it into truncate_document
> then even though
> I can reduce it down to say 100 words, it is lacking words
> like "and" "it"
> and "this" because it has been copied from the
> keyword_document.
That's not true. copy operation is performed before analysis (stopwor
I'm really confused here. I have a document which is say 4000 words long. I
want to get this put into two fields in Solr without having to save the
original document in its entirety within Solr.
When I import my fulltext (4000 word) document to Solr I was going to put it
straight into keyword_docu
The only catch here is that copyField might truncate in the middle of a
word, yielding an improper term.
-- Jack Krupansky
-Original Message-
From: Ahmet Arslan
Sent: Monday, September 17, 2012 11:54 AM
To: solr-user@lucene.apache.org
Subject: Re: Taking a full text, then truncate
--- On Mon, 9/17/12, Spadez wrote:
> From: Spadez
> Subject: Re: Taking a full text, then truncate and duplicate with stopwords
> To: solr-user@lucene.apache.org
> Date: Monday, September 17, 2012, 7:10 PM
> Maybe I dont understand, but if you
> are copying the keyword descr
Maybe I dont understand, but if you are copying the keyword description field
and then truncating it then the truncated form will only have keywords too.
That isnt what I want. I want the truncated form to have words like "a"
"the" "it" etc that would have been removed when added to
keyword_descrip
> The trouble is, I want the truncated desciption to still
> have the keywords.
copyField copies raw text, it has noting to do with analysis.
Thank you for the reply.
The trouble is, I want the truncated desciption to still have the keywords.
If I pass it to the keyword_descipriton and remove words like "and" "i"
"then" "if" etc, then copy it across to truncated_description, my truncated
description will not be a sentance, it will onl
--- On Mon, 9/17/12, Spadez wrote:
> From: Spadez
> Subject: Re: Taking a full text, then truncate and duplicate with stopwords
> To: solr-user@lucene.apache.org
> Date: Monday, September 17, 2012, 5:32 PM
> In an attempt to answer my own
> question, is this a good solution.
In an attempt to answer my own question, is this a good solution.
Before I was thinking of importing my fulltext description once, then
sorting it into two seperate fields in solr, one truncated, one keyword.
How about instead actually importing my fulltext description twice. Then I
can import it
Purely for searching.
The truncated form is just to show to the user as a preview, and the keyword
form is for the keyword searching.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Taking-a-full-text-then-truncate-and-duplicate-with-stopwords-tp4008269p4008295.html
Sent
> I dont want to store this as it is in Solr, I want to
> instead have two
> versions of it. One as a truncated form, and one as a
> keyword form.
> *Truncated Form:*
If truncated form means first N characters then copyField can be used
http://wiki.apache.org/solr/SchemaXml#Copy_Fields
> *Keyw
20 matches
Mail list logo
