Boost fields for more like this query

Hi, I'm using lucene 4.8.1 an try to get the MLT to give certain fields a bigger weight in the similarity calculation. Is this even possible? I only saw that I can give a boost to the MLTQuery itself, but not to a field. Has anybody any idea? Regards, Jürgen. -- Jürgen Albert

Re: Performance of Prefix, Wildcard and Regex queries?

It doesn't matter at all if you try to e.g. optimize a WildcardQuery like foo* into a PrefixQuery, because Lucene turns all of these queries into an AutomatonQuery anyway, which efficiently intersects a term automaton with the terms dictionary. Mike McCandless http://blog.mikemccandless.com On

Re: What does "found existing value for PerFieldPostingsFormat.format" mean?

Additional investigation: The index has two segments. Both segments have this "path-position" in the FieldInfo only once. The settings look the same: FieldInfo in first sub-reader: name = "path-position" number = 6 docValuesType = NONE storeTermVector = false

Re: Creating Queries agnostic to Lucene Versions

Any thought on the below question? On Friday 14 October 2016, Rajnish Kamboj wrote: > Hi > > How can I make my Lucene queries agnostic to Lucene Versions? > > e.g. NumericRangeQuery in 5.3.1 is LegacyNumericRangeQuery in 6.0.0 > (NumericRangeQuery is completely removed) >

Re: What does "found existing value for PerFieldPostingsFormat.format" mean?

Continuation, found a bug but I'm not sure whether it's in Lucene or Lucene's Javadoc. In MultiFields: @SuppressWarnings({"unchecked","rawtypes"}) @Override public Iterator iterator() { Iterator subIterators[] = new Iterator[subs.length]; for(int

What does "found existing value for PerFieldPostingsFormat.format" mean?

Hi all. Does anyone know what this error message means? found existing value for PerFieldPostingsFormat.format, field=path-position, old=Lucene50, new=Lucene50 java.lang.IllegalStateException: found existing value for PerFieldPostingsFormat.format, field=path-position, old=Lucene50,