bq: Does this mean LongField/IntField just supports lexicographic
order in sorting?
no on several counts.
No numeric type (long, int, float, double or trie values) support
lexicographic sorting. That's the whole _point_ of having numeric
types in the first place. Well, and efficient range queries
Thank you Adrien.
"NumericDocValuesField is the one that supports sorting."
Does this mean LongField/IntField just supports lexicographic order in
sorting?
-
Kumaran R
On Dec 22, 2016 11:28 PM, "Adrien Grand" wrote:
Le jeu. 22 déc. 2016 à 18:50, Kumaran Ramasubramanian
a écrit :
> I want
This does not work because FieldValueQuery requires that the field has doc
values, which is not the case on your field apparently.
Le jeu. 22 déc. 2016 à 17:50, Roxana Danger
a écrit :
> Hi all,
>
> I have created an index using solr. I am trying to execute the following
> code, but I get zero r
Le jeu. 22 déc. 2016 à 18:50, Kumaran Ramasubramanian
a écrit :
> I want to provide sorting, range search and faceting in numeric fields.
>
> AFAIK, Purpose of different numeric field types are,
>
> NumericDocValuesField supports sorting and faceting
> LongField/IntField supports range query and
Hi Mukul,
Lucene maintains a number of threadlocals alongside each segment. While
these structures should remain small (a couple tens of KB at most), the
fact we have them per segment and in threadlocals means that overall memory
usage for these structures is linear with the number of threads that
Hi All,
I want to provide sorting, range search and faceting in numeric fields.
AFAIK, Purpose of different numeric field types are,
NumericDocValuesField supports sorting and faceting
LongField/IntField supports range query and sorting
1. Should i duplicate one field in above mentioned type
It would be much slower and scoring does not work as expected.
Full text search engines flatten the data and are fast because of that. Every
additional field structure should also be flattened. To improve search you also
index various stuff redundant, so you use copy fields to achieve that.
Uwe
Why not turning every term int the search into a BooleanQuery listing
all the diferent fields to be searched? Is there a problem with that?
Nicolás.-
El 21/12/16 a las 13:38, Uwe Schindler escribió:
Hi,
This is the standard approach, there is no better way. This also keeps "scoring" working
Hi all,
I have created an index using solr. I am trying to execute the following
code, but I get zero results in the count.
DirectoryReader dr = DirectoryReader.open(FSDirectory.open(new
File(indexDir).toPath()));
IndexSearcher searcher = new IndexSearcher( dr );
System.out.println(dr.maxDoc());
Le 21/12/2016 à 13:27, David Causse a écrit :
But given that some efforts have been done to separate sub scorers
from "top-level" scorers (see
https://issues.apache.org/jira/browse/LUCENE-5487) would it make sense
now to make BulkScorers aware of some time constraints?
Looking a bit closer I
10 matches
Mail list logo
