Handle an existing spantree in exactmatch

This may happen if a field which is indexed is used as an input for another
field indexed as exact match.

1 files changed, 5 insertions, 5 deletions

diff --git a/config-model/src/main/java/com/yahoo/searchdefinition/processing/ExactMatch.java b/config-model/src/main/java/com/yahoo/searchdefinition/processing/ExactMatch.java
index 51751b2e247..d5b22988e36 100644
--- a/config-model/src/main/java/com/yahoo/searchdefinition/processing/ExactMatch.java
+++ b/config-model/src/main/java/com/yahoo/searchdefinition/processing/ExactMatch.java
@@ -58,14 +58,13 @@ public class ExactMatch extends Processor {
             field.addQueryCommand("word");
         } else { // exact
             String exactTerminator = DEFAULT_EXACT_TERMINATOR;
-            if (field.getMatching().getExactMatchTerminator() != null &&
-                ! field.getMatching().getExactMatchTerminator().equals(""))
-            {
+            if (field.getMatching().getExactMatchTerminator() != null
+                && ! field.getMatching().getExactMatchTerminator().equals("")) {
                 exactTerminator = field.getMatching().getExactMatchTerminator();
             } else {
                 warn(search, field,
-                     "With 'exact' matching, an exact-terminator is needed (using \""
-                     + exactTerminator +"\" as terminator)");
+                     "With 'exact' matching, an exact-terminator is needed " +
+                     "(using '" + exactTerminator +"' as terminator)");
             }
             field.addQueryCommand("exact " + exactTerminator);
 
@@ -103,6 +102,7 @@ public class ExactMatch extends Processor {
             }
             return exp;
         }
+
     }
 
 }