[hibernate-issues] [JIRA] (HSEARCH-3947) Avoid creating huge arrays for collectors when a query does not have an upper bound limit

[Yoann Rodière (JIRA)]

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b ) *commented* on HSEARCH-3947 ( https://hibernate.atlassian.net/browse/HSEARCH-3947?atlOrigin=eyJpIjoiNjRiNjc2Yjc2M2I4NGM5YzgyZDNlNjM3Nzg3MTcxMjMiLCJwIjoiaiJ9 )

Re: Avoid creating huge arrays for collectors when a query does not have an upper bound limit ( https://hibernate.atlassian.net/browse/HSEARCH-3947?atlOrigin=eyJpIjoiNjRiNjc2Yjc2M2I4NGM5YzgyZDNlNjM3Nzg3MTcxMjMiLCJwIjoiaiJ9 )

By the way we'd have to check this is still relevant in Search 6, too. Since we split the collection in two phases (one phase to collect topDocs + aggregations, the second to retrieve projections from top docs), this will only be a problem if the topDocs or aggregation collectors size their internal structures according to the limit. If they don't, and use automatically increasing container (List, ...), we're fine.

( https://hibernate.atlassian.net/browse/HSEARCH-3947#add-comment?atlOrigin=eyJpIjoiNjRiNjc2Yjc2M2I4NGM5YzgyZDNlNjM3Nzg3MTcxMjMiLCJwIjoiaiJ9 ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3947#add-comment?atlOrigin=eyJpIjoiNjRiNjc2Yjc2M2I4NGM5YzgyZDNlNjM3Nzg3MTcxMjMiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128- sha1:3143c77 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200611/0003ef3f/attachment.html