-
Notifications
You must be signed in to change notification settings - Fork 340
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
allow for adding custom analyzers to mapping definition #2282
base: 2.10.x
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,6 +68,7 @@ class Field implements FieldInterface | |
'is_used_in_spellcheck' => false, | ||
'search_weight' => 1, | ||
'default_search_analyzer' => self::ANALYZER_STANDARD, | ||
'custom_search_analyzers' => [], | ||
'filter_logical_operator' => self::FILTER_LOGICAL_OPERATOR_OR, | ||
'norms_disabled' => false, | ||
]; | ||
|
@@ -240,6 +241,18 @@ public function getDefaultSearchAnalyzer() | |
return $this->config['default_search_analyzer']; | ||
} | ||
|
||
/** | ||
* {@inheritDoc} | ||
*/ | ||
public function getCustomSearchAnalyzers() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we need some unit testing here, this file is already covered so any new method should also be. |
||
{ | ||
if (is_array($this->config['custom_search_analyzers'])) { | ||
return $this->config['custom_search_analyzers']; | ||
} | ||
|
||
return json_decode($this->config['custom_search_analyzers'], true); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not a huge fan of having json_encoded data being set inside XML file, couldn't it be an XML array either ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. By the way, I think the xsd schema should be updated with this new config node probably. |
||
} | ||
|
||
/** | ||
* {@inheritDoc} | ||
*/ | ||
|
@@ -358,6 +371,7 @@ private function getFieldAnalyzers(): array | |
if ($this->isSearchable() && $this->getSearchWeight() > 1) { | ||
$analyzers[] = self::ANALYZER_WHITESPACE; | ||
$analyzers[] = self::ANALYZER_SHINGLE; | ||
$analyzers = array_merge($analyzers, $this->getCustomSearchAnalyzers()); | ||
} | ||
|
||
if (empty($analyzers) || $this->isFilterable()) { | ||
|
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.
We need additional test cases in unit testing to deal with the fact that we can have custom_analyzers or not.
Actually the existing tests are not failing, which is good, but there is no clue about the expected result if the field is meant to have custom_analyzers