Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Make sure field-value-searches works at field level #405

Closed
dmcassel opened this issue Mar 19, 2015 · 3 comments
Closed

Make sure field-value-searches works at field level #405

dmcassel opened this issue Mar 19, 2015 · 3 comments

Comments

@dmcassel
Copy link
Collaborator

field-value-searches should work at the database level and the field level, but we have a report of it not working at the field level when added to ml-config.xml. This ought to work:

<field>
  <field-name>verladerNummer</field-name> 
  <field-path> 
    <path>PcsRef[CRlTyCd eq "VL"]/PcsRef</path> 
    <weight>1</weight>
  </field-path>
  <word-lexicons/>
  <tokenizer-overrides/>
  <field-value-searches>true</field-value-searches>
  <trailing-wildcard-searches>true</trailing-wildcard-searches>
  <included-elements/>
  <excluded-elements/>
</field>
@grtjn
Copy link
Contributor

grtjn commented Mar 19, 2015

It actually looks like it is supported, but with a different name. It probably works if you use value-searches instead of field-value-searches.

I recommend allowing both though, as field-value-searches is the way ML saves the setting inside databases.xml. Working on a PR for this..

@grtjn grtjn self-assigned this Mar 19, 2015
@grtjn grtjn added this to the 1.7.2 milestone Mar 19, 2015
@grtjn
Copy link
Contributor

grtjn commented Mar 19, 2015

Thnx to @steliann for reporting the issue..

grtjn added a commit to grtjn/roxy that referenced this issue Mar 19, 2015
@grtjn
Copy link
Contributor

grtjn commented Mar 20, 2015

PR pending..

dmcassel added a commit that referenced this issue Mar 20, 2015
Fixed #405: support for field-value-searches on fields
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants