Wildcard in PhraseQuery

Hi All, Can I use wildcard in a phrase query in Lucene/Solr? Can anybody point me some directions to look into? Thanks, Chuming - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail

ANNOUNCE: Lucene/Solr Revolution EU 2013: Registration & Community Voting

(NOTE: cross-posted to various lists, please reply only to general@lucene w/ any questions or follow ups) 2 Announcements folks should be aware of regarding the upcoming Lucene/Solr Revolution EU 2013 in Dublin... # 1) Registration Now Open Registration is now open for Lucene/Solr Revolu

Re: Document boosting and native ordering of results

I had been planning something similar to what Michael was used to: creating a regular numeric field (call it "weight", say) with a rank value, applying a field boost to that field that is equal to the rank value, and then querying with weight:[* TO *] as a term, thinking that would end up bring

Huge FacetArrays while using SortedSetDocValuesAccumulator

Hello, We are working with large lucene 4.3.0 index and using SortedSetDocValuesFacetFields for creating facets and SortedSetDocValuesAccumulator for facet accumulation. We couldn't use a taxonomy based facet implementation (We use MultiReader for searching and our indices is composed of mult

RE: Document boosting and native ordering of results

Hi, This is still possible (in reality it was broken in Lucene version prior 4.0 if you refer to Document.setBoost() -> see changelog/MIGRATE.txt): You have to add an additional DocValues field (a long or double numeric) and use a FunctionQuery / CustomScoreQuery to modify the score based on th

Altering field info without building index from scratch

Hello. We got the error: java.lang.IllegalStateException: field "xxx" was indexed without position data; cannot run PhraseQuery What I suspect is happening is that field xxx was first indexed as a StringField (untokenized), and subsequently changed to TextField (tokenized and analyzed). Ev

Re: Document boosting and native ordering of results

Not sure if there are any thoughts on this. It definitely makes sense to assign a rank to each document in the index, so that all else being equal, documents are returned in order of rank. This is exactly what the page rank is in Google's index, and Google would be lost without it. This used

Boosting potential phrases when using QueryParser

We are using QueryParser.parse(userEnteredQuery) to get a programmatic Query object. We would like to boost documents that contain some of the query terms as "mini phrases". For example, when the user searches for: *professional development leader*, we would like to get back all the documents that

Lucene index files are empty

I want to umplement full text search using Lucene and Hibernate search. As I understand, Lucene creats two files. These two files should be contain some text data, but my index files are empty ( I open these two files with Luke) [image: Inline image 1] here is my code: @Entity@Indexed@Table(name=

Boosting potential phrases when using QueryParser

We are using QueryParser.parse(userEnteredQuery) to get a programmatic Query object. We would like to boost documents that contain some of the query terms as "mini phrases". For example, when the user searches for: *professional development leader*, we would like to get back all the documents that