summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTor Egge <Tor.Egge@yahoo-inc.com>2017-03-27 08:52:15 +0000
committerTor Egge <Tor.Egge@yahoo-inc.com>2017-03-27 08:52:15 +0000
commit88ac24cb3aa5602e3755acb612c4c0fefef17d55 (patch)
treee56834453dee628f9563e8b1ec0f5145517cf132
parentf2d8cf327e614447b10f344007ef82c55ff1737f (diff)
Dense posting list threshold doesn't affect how predicate attribute is saved
or how data is processed in document processors.
-rw-r--r--searchcore/src/vespa/searchcore/proton/attribute/attributemanager.cpp3
1 files changed, 1 insertions, 2 deletions
diff --git a/searchcore/src/vespa/searchcore/proton/attribute/attributemanager.cpp b/searchcore/src/vespa/searchcore/proton/attribute/attributemanager.cpp
index d4b1c589c8c..2b519806248 100644
--- a/searchcore/src/vespa/searchcore/proton/attribute/attributemanager.cpp
+++ b/searchcore/src/vespa/searchcore/proton/attribute/attributemanager.cpp
@@ -48,8 +48,7 @@ bool matchingTypes(const AttributeVector::SP &av, const search::attribute::Confi
if (newConfig.basicType().type() == BasicType::PREDICATE) {
if ((oldConfig.arity() != newConfig.arity()) ||
(oldConfig.lower_bound() != newConfig.lower_bound()) ||
- (oldConfig.upper_bound() != newConfig.upper_bound()) ||
- (oldConfig.dense_posting_list_threshold() != newConfig.dense_posting_list_threshold())) {
+ (oldConfig.upper_bound() != newConfig.upper_bound())) {
return false;
}
}