Closed GoogleCodeExporter closed 8 years ago
This has to do with how Duke finds candidate matches before doing the detailed
matching. This is done by the Database component, and the default Lucene
database requires at least one token to match exactly. If you set (just inside
the root element):
<param name="database-implementation" value="in-memory"/>
all records will be returned as candidates, and matching will work. However,
this database is very slow for large data sets. In Duke 1.2 I add two database
implementations that can produce inexact matches and which are also faster than
the Lucene backend. 1.2 will be released very soon.
Original comment by lar...@gmail.com
on 20 Jan 2014 at 7:00
Thanks for your response. It is working. One quick question, Can you tell me
how and in which class we are using threshold,high,low values to compute and
display the overall probability?
Every comparator returns a probability. Where exactly, is that probability
transformed to different value using high,low values?
Original comment by brindhac...@gmail.com
on 21 Jan 2014 at 9:41
The logic for combining low+high with comparator similarity is in
PropertyImpl.compare. I'm not really satisfied with that, but that's where it
is for now.
Glad it's working!
Original comment by lar...@gmail.com
on 21 Jan 2014 at 1:06
Original issue reported on code.google.com by
brindhac...@gmail.com
on 20 Jan 2014 at 6:48