Skip to content

Conversation

original-brownbear
Copy link
Contributor

There's a number of issues in this one. Opening it to have the fixes for #115056 all in one place
but will merge this through a couple PRs for individual review to make it easier -> WIP

…nects There's a number of issues in this one. Opening it to have the fixes for elastic#115056 all in one place but will merge this through a couple PRs for individual review to make it easier -> WIP
@original-brownbear original-brownbear added >bug WIP :Search/Search Search-related issues that do not fall into other categories labels Oct 26, 2024
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Oct 26, 2024
The results instance does not need to be a field. It's state handling is fairly straight forward, it needs to be released once all fetches have been procesed. No need to even create it on any other path so I split up the method slightly to clearly isolate when and how we need the results instance. Part of elastic#115722
original-brownbear added a commit that referenced this pull request Oct 28, 2024
The results instance does not need to be a field. It's state handling is fairly straight forward, it needs to be released once all fetches have been procesed. No need to even create it on any other path so I split up the method slightly to clearly isolate when and how we need the results instance. Part of #115722
@original-brownbear
Copy link
Contributor Author

closing in favour of #116060

ioanatia pushed a commit to ioanatia/elasticsearch that referenced this pull request Nov 4, 2024
The results instance does not need to be a field. It's state handling is fairly straight forward, it needs to be released once all fetches have been procesed. No need to even create it on any other path so I split up the method slightly to clearly isolate when and how we need the results instance. Part of elastic#115722
jfreden pushed a commit to jfreden/elasticsearch that referenced this pull request Nov 4, 2024
The results instance does not need to be a field. It's state handling is fairly straight forward, it needs to be released once all fetches have been procesed. No need to even create it on any other path so I split up the method slightly to clearly isolate when and how we need the results instance. Part of elastic#115722
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Nov 22, 2024
The results instance does not need to be a field. It's state handling is fairly straight forward, it needs to be released once all fetches have been procesed. No need to even create it on any other path so I split up the method slightly to clearly isolate when and how we need the results instance. Part of elastic#115722
elasticsearchmachine pushed a commit that referenced this pull request Nov 22, 2024
The results instance does not need to be a field. It's state handling is fairly straight forward, it needs to be released once all fetches have been procesed. No need to even create it on any other path so I split up the method slightly to clearly isolate when and how we need the results instance. Part of #115722
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Search/Search Search-related issues that do not fall into other categories v9.0.0 WIP

2 participants