duplicates - Solr Deduplication (dedupe) giving all zeros in signatureField -


i've followed examples listed in documentation here: http://wiki.apache.org/solr/deduplication , https://cwiki.apache.org/confluence/display/solr/de-duplication

however, when analyzing results every signaturefield gets returned so: 0000000000000000

i can't seem figure out why unique signature isn't being generated.

relevant config sections:

solrconfig.xml

 <requesthandler name="/update"               class="solr.xmlupdaterequesthandler"> <!-- see below information on defining      updaterequestprocessorchains can used name      on each update request   -->     <lst name="defaults">      <str name="update.chain">dedupe</str>    </lst>  </requesthandler>

...

<!-- deduplication     example dedup update processor creates "id" field    on fly based on hash code of other fields.     example has overwritedupes set false since using    id field signaturefield , solr maintain    uniqueness based on anyway.  -->   <updaterequestprocessorchain name="dedupe">    <processor class="solr.processor.signatureupdateprocessorfactory">      <bool name="enabled">true</bool>      <str name="signaturefield">signaturefield</str>      <bool name="overwritedupes">false</bool>      <str name="fields">name,features,cat</str>      <str name="signatureclass">solr.processor.lookup3signature</str>    </processor>    <processor class="solr.logupdateprocessorfactory" />    <processor class="solr.runupdateprocessorfactory" />  </updaterequestprocessorchain>

schema.xml

     <fields>    <!-- valid attributes fields:      name: mandatory - name field      type: mandatory - name of defined type        <types> section      indexed: true if field should indexed (searchable or sortable)      stored: true if field should retrievable      multivalued: true if field may contain multiple values per document      omitnorms: (expert) set true omit norms associated        field (this disables length normalization , index-time        boosting field, , saves memory).  full-text        fields or fields need index-time boost need norms.        norms omitted primitive (non-analyzed) types default.      termvectors: [false] set true store term vector        given field.        when using morelikethis, fields used similarity should        stored best performance.      termpositions: store position information term vector.        increase storage costs.      termoffsets: store offset information term vector.        increase storage costs.      default: value should used if no value specified        when adding document.    -->     <field name="signaturefield" type="string" stored="true" indexed="true" multivalued="false" />    <field name="id" type="string" indexed="true" stored="true" required="true" />    <field name="sku" type="text_en_splitting_tight" indexed="true" stored="true" omitnorms="true"/>    <field name="name" type="text_general" indexed="true" stored="true"/>    <field name="alphanamesort" type="alphaonlysort" indexed="true" stored="false"/>    <field name="manu" type="text_general" indexed="true" stored="true" omitnorms="true"/>    <field name="cat" type="string" indexed="true" stored="true" multivalued="true"/>    <field name="features" type="text_general" indexed="true" stored="true" multivalued="true"/> ... etc

i'm wondering if can steer me in right direction?


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more