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
This is happening on version 0.12.1. When highlighting is specified, some of the highlight fields come complete, and some are broken. When those documents are access directly by providing the direct index as "from" and setting "size" as 1, it comes fine: Reproduce code is below (bash script):
curl -XPUT 'http://server:9200/indexname/highbug/_mapping' -d '
{
"highbug":
{
"properties":
{
"body":
{
"store": "yes",
"term_vector": "with_positions_offsets",
"type": "string"
},
"title":
{
"store": "yes",
"term_vector": "with_positions_offsets",
"type": "string"
}
}
}
}
';
for (( i = 0; i < 20; ++i ))
do
curl -XPUT "http://server:9200/indexname/highbug/$i" -d "
{
\"body\": \"Test body\",
\"date\": \"$(date +%s)\",
\"title\": \"This is a test on the highlighting bug present in elasticsearch\"
}";
done
The call below returns the full highlighted fragment for the 1st and 5th results, and the 2nd through 4th results return "hting bug present in elasticsearch" instead of "This is a test on the highlighting bug present in elasticsearch".
This is happening on version 0.12.1. When highlighting is specified, some of the highlight fields come complete, and some are broken. When those documents are access directly by providing the direct index as "from" and setting "size" as 1, it comes fine: Reproduce code is below (bash script):
The call below returns the full highlighted fragment for the 1st and 5th results, and the 2nd through 4th results return "hting bug present in elasticsearch" instead of "This is a test on the highlighting bug present in elasticsearch".
The text was updated successfully, but these errors were encountered: