-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add new fieldtypes for dict score modifiers #241
Conversation
@@ -97,7 +97,7 @@ def test_valid_score_modifiers_format(self): | |||
"add_to_score": [ | |||
{"field_name": "add_1", "weight" : -3, | |||
}, | |||
{"field_name": "add_2", "weight": 1, | |||
{"field_name": "add_2.a", "weight": 1, | |||
}] | |||
} | |||
self.search_with_score_modifier(score_modifiers=valid_score_modifiers) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no assertion in this test. what is the expected behaviour?
"add_to_score": [ | ||
{"field_name": "add_1", "weight" : 4, | ||
}, | ||
{"field_name": "add_2", "weight": 1, | ||
{"field_name": "add_2.a", "weight": 1, | ||
}] | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the assertion for this test is too wide. we should at least test the error code and some key word in the response if there's any
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor issue of an existing test. not related to your change.
|
||
# NOTE: This isn't used anywhere |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So why do we need this if it's not used in any places?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't totally remove def supported_marqo_version()
yet as someone might have a comment on its use.
__marqo_version__
is removed though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
No
FieldTypes
defined for map score modifiersWhat is the new behavior (if this is a feature change)?
Added 4 new map numeric fieldtypes for dictionary score modifiers. Removed superfluour
__marqo_version__
variableDoes this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: