What to do with Lucene Version parameter on upgrade

I'm relatively new to Lucene and am in the process of upgrading from 4.0 to 4.3.1. I'm trying to figure out if I need to leave my version at LUCENE_40 or if it is safe to change it to LUCENE_43. Does this parameter directly determine the index format? I have some existing indexes from 4.0

Re: What to do with Lucene Version parameter on upgrade

Version relates to analyzers and the like rather than to internals such as index format. I don't recall what exactly has changed between 4.0 and 4.3.1 but you're probably safe to change it and use LUCENE_43. Take a look at the javadoc for StandardAnalyzer - that lists some versions and what

Payload Matching Query

Hi guys, I am trying to figure out whether there is a query that would do matching based od token payloads. JUST on token payloads. I think, there is not such query. Thus, I thought about implementing one, but somehow I dont know where to start. I've been trying to achieve this by extending

build of trunk hangs

I'm trying to build trunk and when I run ant compile the build hangs right after Building replicator at the line common.resolve:. (see below for more context) I'm not familiar with Ivy so I'm not too sure where to look for the problem. Can someone point me to the FAQ or the appropriate resource

Re: build of trunk hangs

Hi, On Thu, Jun 20, 2013 at 5:59 PM, Tom Burton-West tburt...@umich.edu wrote: I'm trying to build trunk and when I run ant compile the build hangs right after Building replicator at the line common.resolve:. (see below for more context) I'm not familiar with Ivy so I'm not too sure where

Re: Payload Matching Query

Hi Michal, Although payloads can be used at query time to customize scoring, they can't be used for searching. Lucene only allows to search on terms. -- Adrien - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org

Re: Payload Matching Query

Hi Adrien, thanks for your reply. If payloads cannot be used for searching, is there any workaround how to achieve similar functionality? What I'd like to accomplish is to be able to search documents with contents for example W. A. Mozart[artist] was born in Salzburg[city] just by specifying the

Re: Payload Matching Query

Any reason not to have separate artist and city fields? So you would search for: artist:(W. A. Mozart) city:Salzburg HTH Brendan On Thu, Jun 20, 2013 at 12:27 PM, michal samek samek.mic...@gmail.comwrote: Hi Adrien, thanks for your reply. If payloads cannot be used for searching, is there

Re: Payload Matching Query

Well, with this solution you won't be able to search for near occurences of payloads - as with NearSpanQueries :-/ I just need to store some searchable data with terms, not with documents. But why not implement totally new Query? I'm very new to Lucene, so I've got no idea what it involves, how

Re: Payload Matching Query

There are several ways to implement it : Query as you mentioned. You'd need to implement a Scorer which traverses the posting list where the payload exists. The methods you should implement are nextDoc() and advance(). You'll also need to traverse DocsAndPositionsEnum. A Filter. That's somewhat

Re: TestGrouping.Java seems to combine multiple tests into one huge test

Sine my objective is to undersdand BlockGroupingCollector, I thought I would extract a test for BlockGroupingCollector, maybe in another file as Robert suggested. I was looking at testRandom because that is where BlockGroupingCollector is tested, but it looks to me like some trickery is involved

Re: segments and sorting

Thanks. If I end up doing it, we can try to get it in. Sriram. On Wed, Jun 19, 2013 at 1:10 AM, Adrien Grand jpou...@gmail.com wrote: Hi, On Wed, Jun 19, 2013 at 12:16 AM, Sriram Sankar san...@gmail.com wrote: Is it possible to do this more efficiently using a merge sort? Assuming the