- 
                Notifications
    You must be signed in to change notification settings 
- Fork 25.6k
Fix synthetic source bug that would mishandle nested dense_vector fields #122425
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
Fix synthetic source bug that would mishandle nested dense_vector fields #122425
Conversation
| Hi @benwtrent, I've created a changelog YAML for you. | 
| Pinging @elastic/es-search-relevance (Team:Search Relevance) | 
| Pinging @elastic/es-storage-engine (Team:StorageEngine) | 
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 from my side
| Hi @benwtrent, I've updated the changelog YAML for you. | 
| 💔 Backport failed
 You can use sqren/backport to manually backport by running  | 
…lds (elastic#122425) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: elastic#122383
…lds (elastic#122425) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: elastic#122383 (cherry picked from commit f5c901e)
| 💚 All backports created successfully
 Questions ?Please refer to the Backport tool documentation | 
…lds (elastic#122425) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: elastic#122383 (cherry picked from commit f5c901e)
…lds (#122425) (#122434) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: #122383
…lds (#122425) (#122437) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: #122383 (cherry picked from commit f5c901e)
…lds (#122425) (#122436) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: #122383 (cherry picked from commit f5c901e)
…or fields (#122425) (#122435) * Fix synthetic source bug that would mishandle nested dense_vector fields (#122425) When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values. While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs. closes: #122383 (cherry picked from commit f5c901e) * fixing backport
When utilizing synthetic source with nested fields, we attempt to rebuild the child values in addition to all the parent values.
While this generally works well, its potential that certain values might be missing from various child docs. Consequently, we will attempt to iterate the vector values strangely, resulting in seemingly missing values or potentially exceptions indicating EOFs.
closes: #122383