Oops, sorry for the "Solr" answer. In Lucene you need to simply index the
same value, once as a raw string and a second time as a tokenized text
field. Grouping would use the raw string version of the data.
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Monday, Febru
Okay, so, fields that would normally need to be tokenized must be stored as
both raw strings for grouping and tokenized text for keyword search. Simply
use copyField to copy from one to the other.
-- Jack Krupansky
-Original Message-
From: Ramprakash Ramamoorthy
Sent: Monday, Februar
On Mon, Feb 18, 2013 at 9:47 PM, Jack Krupansky wrote:
> Please clarify exactly what you want to group by - give a specific example
> that makes it clear what terms should affect grouping and which shouldn't.
>
Assume I am indexing a library data. Say there are the following fields for
a particul
Hi,
Why not having the IS#close() calling the wrapped IR#close() ?
I would be happier having to only deal with the Searcher once created
and forget it wraps a Reader: I create a Searcher, I close it.
Thx, Eric
On 18/02/2013 22:20, Simon Willnauer wrote:
On Mon, Feb 18, 2013 at 7:32 PM, saisa
On Thu, Feb 14, 2013 at 11:42 AM, VIGNESH S wrote:
> Hi,
>
> I have two questions
>
> 1.How to Get the enumeration of Terms Ending with a given word
> I saw we can get enumerations of word starting at a given word by
> Indexreader.terms(term())) method
unless you want to iterate all terms and che
On Mon, Feb 18, 2013 at 7:32 PM, saisantoshi wrote:
> I understand from the JIRA ticket(Lucene-3640) that the IndexSearcher.close()
> is no-op operation but not very clear on why it is a no-op? Could someone
> shed some light on this? We were using this method in the older versions and
> is it saf
Hello community,
i am doing an evaluation in the context of CJK. I compare some indexing
strategies like "unigram", "bigram", "unigram + bigram" and "word based"
indexing.
1.
I used the Standardanalyzer for "unigram". I think it works for chinese but
it is doing some other staff for Japanese and
I understand from the JIRA ticket(Lucene-3640) that the IndexSearcher.close()
is no-op operation but not very clear on why it is a no-op? Could someone
shed some light on this? We were using this method in the older versions and
is it safe now to remove this call. Just want to understand the conseq
On 18/02/2013 16:26, Uwe Schindler wrote:
The problem is:
Lucene has never supported *real* per-document boosts. Those boosts were always
per-field. As we only work per-field, it depends on the query how your results
score. If you have a TermQuery, the per-field boost is used (the one from the
The problem is:
Lucene has never supported *real* per-document boosts. Those boosts were always
per-field. As we only work per-field, it depends on the query how your results
score. If you have a TermQuery, the per-field boost is used (the one from the
field queried), but e.g. if you have anothe
Please clarify exactly what you want to group by - give a specific example
that makes it clear what terms should affect grouping and which shouldn't.
-- Jack Krupansky
-Original Message-
From: Ramprakash Ramamoorthy
Sent: Monday, February 18, 2013 6:12 AM
To: java-user@lucene.apache.o
On 18/02/2013 16:04, Uwe Schindler wrote:
It is not a regression, as per-Document boost were never working correctly. If you want
to boost documents in a consistent way (and make their scores in search results really
using that factor), you should index a DocValues field and use that in a Custo
It is not a regression, as per-Document boost were never working correctly. If
you want to boost documents in a consistent way (and make their scores in
search results really using that factor), you should index a DocValues field
and use that in a CustomScoreQuery to boost the results with that
On 18/02/2013 13:41, Ian Lea wrote:
See the migration guide:
"If you previously used Document.setBoost, you must now pre-multiply
the document boost into each Field.setBoost. If you have a
multi-valued field, you should do this only for the first Field
instance (ie, subsequent Field instance sha
I am out of the office until 20/02/2013.
For Search/CCM - Noga Tor
For AS-Search/Social People Typeahead - Sharon Krisher
Or my manager Eitan Shapiro.
Note: This is an automated response to your message "What is equivalent to
Document.setBoost() from Lucene 3.6 inLucene 4.1 ?" sent on 18/02/20
See the migration guide:
"If you previously used Document.setBoost, you must now pre-multiply
the document boost into each Field.setBoost. If you have a
multi-valued field, you should do this only for the first Field
instance (ie, subsequent Field instance sharing the same field name
should only i
What is equivalent to Document.setBoost() from Lucene 3.6 inLucene 4.1 ?
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
17 matches
Mail list logo
