You're creating the TopScoreDocCollector with numHits=1. This means the
collector only retains one result, but keep track of the total number of
results. Imagine a situation where there's a million hits. You want to know
the number, but you usually don't need all their doc ids.
That's why scoreDoc
I could kick myself in the head for that oneduh...that worked! Thanks!!!
I should have tried that earlier from your earlier email but for some reason I
was stuck on trying to get * working.
Thanks,
Dean
-Original Message-
From: Michael Sokolov [mailto:soko...@ifactory.com]
Sent: S
On 6/19/2011 8:11 PM, Hiller, Dean x66079 wrote:
Oddly, enough, this seems to work and I get one result calling
Collector.collect(int docIt)...(I found out AND has to be caps)...
author:dean AND date:20110623
but this does not seem to work...
author:dean AND date:[ 20110623 TO * ]
I'm not sur
Oddly, enough, this seems to work and I get one result calling
Collector.collect(int docIt)...(I found out AND has to be caps)...
author:dean AND date:20110623
but this does not seem to work...
author:dean AND date:[ 20110623 TO * ]
You would think this second query would return the single res
Swt, * worked, but SHUCKS.query completely returns no results. I don't
get it...it gets into the lucene code and since there is no "Scorer" returned,
it seems to skip over any results that would be valid :(any ideas what is
wrong with this program
MyCollector.collect(int docId)
I think you need
field:[20020101 TO *]
although the "*" option isn't available in some versions (pre 3.1?) and
you just have to supply a big value:
field:[20020101 TO ]
-Mike
On 6/19/2011 6:18 PM, Hiller, Dean x66079 wrote:
"here you can simply go for field:[20020101 TO ] and leave
"here you can simply go for field:[20020101 TO ] and leave the end
blank. If you want to do fast numeric searches you should use
NumericRangeQuery instead."
I tried that and got an exception...
I need to do something like String queryStr = "author:dean and date:[" + date1
+ " TO ]"; so can I do
No need to score at all. Just need paging and typically it is a loop since
this is an overnight batch job pairing up a trade with one or many trades on a
nosql system. We do need a sorted order as well so we kind of want to
1. have something like ScrollableResultSet
2. be able to pass in order
So do you need to score the documents or can they be in arbitrary order?
On Sun, Jun 19, 2011 at 8:45 PM, Hiller, Dean x66079
wrote:
> Hmmm, maybe I am using the wrong library?
>
> See the post I just sent especially on the hibernate section where in
> hibernate
> you can do select * from xxx w
Hmmm, maybe I am using the wrong library?
See the post I just sent especially on the hibernate section where in hibernate
you can do select * from xxx where yyy and page the results(gets slower and
slower
as you go to the nth page) vs. using ScrollableResultSet in hibernate which
does
not get a
I have a JUnit test case so I can demonstrate Lucene to myself. It correctly
returns a hit count of 2 but then when I get the docs, there is only ONE, and I
can't seem to get the info on the 2nd hit at all. Notice my logs print 2 and 1
if you run this example on the counts...
getTotalHits = 2
"It supports it like 2.9, but not using the Hits API. As described above, to
show results 991 to 1000 request the top-1000 results and display the last
10 :-)"
Bear with me as I am little confused so let me throw some stuff down here and
think out loud...
So, I basically have to request the top 1
> I am wondering how the old Hits object worked that was deprecated and
> removedthat looks like I could stop asking it for more results and it
would
> work better not counting all activities that matched in my 10 mil or 100
mil
> result set and just returning the first 100, second 100 and then
More on the below issue. We have perhaps 10 million or 100 million but this
new 3.x lucene appears to go over all the entries that match instead of just
having a cursor into the index??? The more I look at the code, it almost looks
like it is not possible.
I am wondering how the old Hits obje
On Sun, Jun 19, 2011 at 7:29 PM, Hiller, Dean x66079
wrote:
> On the link
> http://lucene.apache.org/java/3_0_3/queryparsersyntax.html#Range%20Searches
>
>
> There is ranged searched, how do I specify everything above a date from date
> 20020101 to end of time?
here you can simply go for field
On Sun, Jun 19, 2011 at 5:39 PM, Saurabh Gokhale
wrote:
> Yes, it makes sense. So in the case of No_Norm I suppose, all the fields
> small or large, are treated the same instead of as per their sizes and
> implicit boost factor.
well yes they will use TF / IDF for scoring additional length
normal
On the link
http://lucene.apache.org/java/3_0_3/queryparsersyntax.html#Range%20Searches
There is ranged searched, how do I specify everything above a date from date
20020101 to end of time?
Next, I am temporarily using lucene in a noSQL solution(to switch to Solr later
after prototype) and
Yes, it makes sense. So in the case of No_Norm I suppose, all the fields
small or large, are treated the same instead of as per their sizes and
implicit boost factor.
Thanks for the explanation
Saurabh
On Sun, Jun 19, 2011 at 9:26 AM, Simon Willnauer <
simon.willna...@googlemail.com> wrote:
> i
if you use norms lucene uses the boost of the fields / document and
multiplies it with a length normalization factor -> 1.0 /
Math.sqrt(numTerms) so you scores should be different. Does that
explain what you are seeing?
Simon
On Sun, Jun 19, 2011 at 7:06 AM, Saurabh Gokhale
wrote:
> Hi All,
> I
Am 18.06.11 19:05, schrieb Steven A Rowe:
Hi Hamada,
Do you know about the Lucene demo?:
http://lucene.apache.org/java/3_2_0/demo.html
also you might want to use
http://code.google.com/p/luke/
in order to view your search index and check what fields it actually
contains
HTH
Michael
Ste
20 matches
Mail list logo
