Store the term value as payload, and score with it.
On Mon, Mar 4, 2013 at 10:10 AM, Sharon Tam wrote:
> Hi,
>
> I have generated my own term-frequency vector representations of documents
> and would like to be able to query these with term-frequency vector queries
> instead of a text-string que
Hi.
I want indexing all documents once a day and after indexing delete old
index files that indexed before a day.
I think to do this, indexing all documents in new directory and replace
IndexSearcher and IndexWriter with olds, and delete old index directory.
Is there more good indexing strategy?
Phew, thanks for bringing closure!
Mike McCandless
http://blog.mikemccandless.com
On Mon, Mar 4, 2013 at 6:00 PM, Konstantyn Smirnov wrote:
> Ah yes, my bad!
>
> I indeed used my own fieldTypes for my numeric fields.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.c
Ah yes, my bad!
I indeed used my own fieldTypes for my numeric fields.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Lucene-4-1-IntField-cannot-be-found-by-a-NumericRangeFilter-NumericRangeQuery-tp4044544p4044670.html
Sent from the Lucene - Java Users mailing list archiv
Hello Oliver,
We are very interested in group sorting based on some aggregation function
also. Would you consider contributing your code to Lucene, or posting your
results?
Tom
Tom Burton-West
Information Retrieval Programmer
Digital Library Production Service
University of Michigan Library
http
Hi,
I have generated my own term-frequency vector representations of documents
and would like to be able to query these with term-frequency vector queries
instead of a text-string query. Is there anyway to bypass the Lucene
preprocessing that occurs in the indexing of documents and queryparsing t
100 terms in a boolean query is not so costly. You could wrap that query in
a ConstantScoreQuery to avoid the score calculation.
Why do you have separate indexes? It would be better to build a single
document and index+store it on a single index.
Thanks
Emmanuel
2013/3/1 Ramprakash Ramamoorthy
On Mon, Mar 4, 2013 at 11:28 AM, Konstantyn Smirnov wrote:
> changing FT to indexed=true did the trick, thanks
>
> Shouldn't it be enabled by default?
It should be, and I think it is, so now I'm confused/worried why you
see it not enabled for indexing by default.
This is how IntField inits its T
changing FT to indexed=true did the trick, thanks
Shouldn't it be enabled by default?
If I invert a field using one of numeric classes, I'd expect it to be
indexed.
Otherwise I would use a StringField or StoredField...
--
View this message in context:
http://lucene.472066.n3.nabble.com/Lucene
The field is not indexed (see the debug output, it says indexed = false).
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Konstantyn Smirnov [mailto:inject...@yahoo.com]
> Sent: Monday, March 04, 2013 5:
Hi guys,
On my path of migrating from 3.6.x to 4.1, I'm facing the following problem:
I create a document with an IntField in it:
doc.add new IntField( 'freeSeats', 5, Store.YES )
After adding to the doc and writing to the index, the field looks like
(copied from eclipse debugger):
[20]Int
11 matches
Mail list logo