I got confused of proximity search. I am getting different results for the
queries TTL "test device "~2 and TTL "device test "~2
I expect same result for the above two queries. Is there any importanThanks Daniel
I 'm using Searcher.explain() & luke to try to understand the reasons for the score.
From Daniel Naber [mailto lucenelist2007@(protected)]
Sent 01 Novem u?vw?u????-????M ??xN???yh?
???u??m?? ?Mw??w??.???z?9?|?M ?? ??r???????q?h????i??g????j+z?^?k ??Z?+l??+z+%??j[a??!??(???????????^??j?l
> but you should have a look at Searcher.explain()
I was half-expecting this answer. (
The query is very basic and the scoring seems completely arbitrary.
Documents with the same number What is the appropriate way of achieving both stopwords and stemming of
stopwords when the MoreLikeThis class is used? My analyzer
(MoreLikeThis.setAnalyzer) uses the Snowball filter and is initialOn Wednesday 10 October 2007 18 44 lucene_user wrote
> I would like to score a single document from a corpus based on a given
> query. The formula score(q d) is basically what I am looking for.
> I have only taken passing glances at Solr so I am afraid I cannot be of
much help. Certainly one of the Solr guys will be able to be of
Since Qsol generates Query objects you j
I would like to score a single document from a corpus based on a given query.
The formula score(q d) is basically what I am looking for.
Pseudo Code of Something Close to what I am looking for
On Oct 10 2007 at 9 51 AM pp1907@(protected) wrote
> Yes image field is binary. However image size is not more than
> 1KB. We would use a combination of text search to narrow down the
On Wed October 10 2007 Martin Dietze wrote
> > Qsol myhardshadow.com/qsol (A query parser I wrote that has fully
> > customizable precedence support - don 't be fooled by the stale websitYes image field is binary. However image size is not more than 1KB. We would use a combination of text search to narrow down the results. But once we get the results we would want to search all imaThe best place is the Lucene website including the wiki and the
javadocs. Is there something in particular you are interested in?
On Oct 10 2007 at 4 05 AM Raghu Ram wrote
> Is thereMark
this reply was just in time )
On Wed October 10 2007 Mark Miller wrote
> Precedence QueryParser (I think its in Lucene contrib packages - I don 't
> believe its perfect but I have not tOn Tue October 09 2007 Daniel Naber wrote
> The operator precedence is known to be buggy. You need to use parenthesis
> e.g. (aa AND bb) OR (cc AND dd)
This would be fine with me but unfortuna
Yes you should close the indices before adding them. Both of the addIndexes*
methods that take Directory require that there are no writers changing the
index in those directories.
They do not acThere is a lot on this topic if you search the archives.
Things to check out
Precedence QueryParser (I think its in Lucene contrib packages - I don 't
believe its perfect but I have not tried it)
The IndexMergeTool (see url below) creates a new index the "mergedIndex ".
Do the other indexes "index1 " "index2 " etc need to be closed
before performing the merge?
This is the same as asking > I have a question that I can 't quite seem to find the answer to by
> googling or searching the archives of this mailing list. The problem
> is I would like to weight some fields more than others. AsHi Scott
Would indexing time field boosts work for you?
"Scott Phillips " wrote
> Hi everyone
> I have a question that I Is there any document or book that discusses lucene internal details ????
On 10/10/07 Peter W. <peter@(protected) > wrote
> The quality of first LIA really shined even for
> thoHi everyone
I have a question that I can 't quite seem to find the answer to by
googling or searching the archives of this mailing list. The problem
is I would like to weight some fields more than otCool!
The quality of first LIA really shined even for
those familiar with Java but new to assertions
and unit tests. Can 't wait to buy LIA2...
Please accept the request to include FieldSelector
We are a startup in the web indexing space. We are looking for an
experienced search engine developer for our team. We are using Solr and
Lucene but search is search and solid experience with aOn Tuesday 09 October 2007 09 55 Martin Dietze wrote
> I 've been going nuts trying to use LuceneParser parse query
> strings using the default operator AND correctly
The operator precedence is kPeter - LIA2 is in progress! ) LIA2IP?
Otis (hi Erik! ))
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http //www.simpy.com/ - Tag - Search - Share
----- Original MeHello
How is progress on the new Lucene in Action coming?
WooHoo! That 's good news.
Now I seee the ConstantScoreRangeQuery in QueryParser.getRangeQuery.
So all I have to do is over-ride QueryParser.getWildcardQuery.
From mark haNote that as of Lucene 2.1 QueryParser was changed to use RangeFilters in place of RangeQuerys by default.
You can simply subclass QueryParser to override construction of wildcardQuerys etc. These meI 'm currently using rangeFilter 's and queryWrapperFilter 's to get around
the max boolean clause limit.
A couple of questions concerning this
1) Is it good design practice to substitue every term coI think you shouldn 't worry about it until you can demonstrate that
you actually have a space problem. Worrying about storing
an extra < 3M is almost certainly a waste of time.
What evidence do you h|