Recently i am working on a problem like this too. I couldn’t find any formal documentation about this issue but when i investigate the results with “explain api”, it seems like “queryNorm” is not applied to the score directly coming from “functions” field. This means that you can not directly normalize script value. However, i … Read more
Yo can make Lucene ignore the special characters by sanitizing the query with something like query = QueryParser.Escape(query) If you do not want your users to ever use advanced syntax in their queries, you can do this always. If you want your users to use advanced syntax but you also want to be more forgiving … Read more
You have various problems with what you pasted: 1) Incorrect mapping When creating the index, you specify: “mappings”: { “files”: { But your type is actually file, not files. If you checked the mapping, you would see that immediately: curl -XGET ‘http://127.0.0.1:9200/files/_mapping?pretty=1’ # { # “files” : { # “files” : { # “properties” : … Read more
-field:[* TO *] In SolrNet, use a negated SolrHasValueQuery
Use field:(value1 value2 value3) or if your default operator is AND then use field:(value1 OR value2 OR value3)
The problem you are facing in the ‘wicket’ example is called entity disambiguation, not entity extraction/recognition (NER). NER can be useful but only when the categories are specific enough. Most NER systems doesn’t have enough granularity to distinguish between a sport and a software project (both types would fall outside the typically recognized types: person, … Read more
Here’s what I’m using. Is this canonical? Is there a better way? SolrQuery q = new SolrQuery(“*:*”); q.setRows(0); // don’t actually request any data return server.query(q).getResults().getNumFound();
Store.Yes Means that the value of the field will be stored in the index Store.No Means that the value of the field will NOT be stored in the index Store.Yes/No does not affect the indexing or searching with lucene. It just tells lucene if you want it to act as a datastore for the values … Read more
The Lucene index is split into smaller chunks called segments. Each segment is its own index. Lucene searches all of them in sequence. A new segment is created when a new writer is opened and when a writer commits or is closed. The advantages of using this system are that you never have to modify … Read more
Turns out this is happening because the mapping needs to be applied to the type: I tried applying it to the wrong thing: curl -XPUT 10.160.86.134:9200/products/_mapping -d ‘{ It needs to be applied to the type like so: curl -XPUT 10.160.86.134:9200/products/product/_mapping -d ‘{ It’s sad that a simple google search couldn’t answer this. Also the … Read more