You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of per_field_analyzer is to get a term vector as created by an analyzer different from the one the field is indexed with. I would expect to get a term vector for a field even if it does not have term vectors stored. Instead I get an NPE:
POST test/doc/1
{
"text": "I am a happy hippo"
}
GET test/doc/1/_termvectors
{
"per_field_analyzer": {
"text": "keyword"
}
}
If I set "term_vector": "yes", in the mapping first all works as expected:
PUT test
{
"mappings": {
"doc": {
"properties": {
"text": {
"term_vector": "yes",
"type": "string"
}
}
}
}
}
POST test/doc/1
{
"text": "I am a happy hippo"
}
GET test/doc/1/_termvectors
{
"per_field_analyzer": {
"text": "keyword"
}
}
Tested with elasticsearch version 2.2
The purpose of
per_field_analyzer
is to get a term vector as created by an analyzer different from the one the field is indexed with. I would expect to get a term vector for a field even if it does not have term vectors stored. Instead I get an NPE:If I set
"term_vector": "yes"
, in the mapping first all works as expected:results in (as expected):
The text was updated successfully, but these errors were encountered: