[SOLR-11209] Upgrade HttpClient to 4.5.3 #230
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
https://issues.apache.org/jira/browse/SOLR-11209 was released in Solr 7.3, so this PR can be closed. |
cpoerschke
pushed a commit
to cpoerschke/lucene-solr
that referenced
this pull request
Apr 5, 2019
* sketch: [SkipSecondStep]SearchGroupShardResponseProcessor with inner [SkipSecondStep]SearchGroupsContainer helper class * sketch: remove/replace SearchGroupsResultTransformer.getInstance * Callers instead directly allocate either DefaultSearchResultResultTransformer or SkipSecondStepSearchResultResultTransformer. * A next step could be the proposed SearchGroupsResultTransformer.SkipSecondStepSearchResultResultTransformer inner class to become a SkipSecondStepSearchResultResultTransformer.java class of its own and the proposed SearchGroupsResultTransformer.DefaultSearchResultResultTransformer inner class to _not_ be created with backcompat considerations in mind e.g. SearchGroupsResultTransformer to not become abstract and its constructor to remain public. This assumes that SearchGroupsResultTransformer would require only simple changes to make it extensible and that then SkipSecondStepSearchResultResultTransformer could extend it.
cpoerschke
pushed a commit
to cpoerschke/lucene-solr
that referenced
this pull request
Jun 14, 2019
* sketch: [SkipSecondStep]SearchGroupShardResponseProcessor with inner [SkipSecondStep]SearchGroupsContainer helper class * sketch: remove/replace SearchGroupsResultTransformer.getInstance * Callers instead directly allocate either DefaultSearchResultResultTransformer or SkipSecondStepSearchResultResultTransformer. * A next step could be the proposed SearchGroupsResultTransformer.SkipSecondStepSearchResultResultTransformer inner class to become a SkipSecondStepSearchResultResultTransformer.java class of its own and the proposed SearchGroupsResultTransformer.DefaultSearchResultResultTransformer inner class to _not_ be created with backcompat considerations in mind e.g. SearchGroupsResultTransformer to not become abstract and its constructor to remain public. This assumes that SearchGroupsResultTransformer would require only simple changes to make it extensible and that then SkipSecondStepSearchResultResultTransformer could extend it.
cpoerschke
pushed a commit
to cpoerschke/lucene-solr
that referenced
this pull request
Aug 6, 2019
…gas patch)
Summary:
In cases where we do grouping and ask for {{group.limit=1}} only it is possible to skip the second grouping step. In our test datasets it improved speed by around 40%.
Essentially, in the first grouping step each shard returns the top K groups based on the highest scoring document in each group. The top K groups from each shard are merged in the federator and in the second step we ask all the shards to return the top documents from each of the top ranking groups.
If we only want to return the highest scoring document per group we can return the top document id in the first step, merge results in the federator to retain the top K groups and then skip the second grouping step entirely.
QueryComponent: interim 'make it compile (somehow)' change (apache#228)
add SearchGroupsContainer (apache#230)
factor out SearchGroupsResultTransformer.serializeOneSearchGroup method (Christine)
Refactor transformToNative adding deserializeOneSearchGroup
increase GroupParams.GROUP_SKIP_DISTRIBUTED_SECOND use (see also 6bdf87)
Remove error logging in allowSkipSecondGroupingStep
Check that withinGroupSort is a prefix of groupSort
SkipSecondStepSearchGroupShardResponseProcessor.addSearchGroupToShards now leaves ShardDoc.fields null
factor out TopGroupsShardResponseProcessor.fillResultIds method
Add regression test group.main=true and group.format=simple
Improve GroupingSpecification validation adding validate() method
SkipSecondStepSearchResultResultTransformer.serializeOneSearchGroup tweaks
cpoerschke
pushed a commit
to cpoerschke/lucene-solr
that referenced
this pull request
Sep 6, 2019
…gas patch)
Summary:
In cases where we do grouping and ask for {{group.limit=1}} only it is possible to skip the second grouping step. In our test datasets it improved speed by around 40%.
Essentially, in the first grouping step each shard returns the top K groups based on the highest scoring document in each group. The top K groups from each shard are merged in the federator and in the second step we ask all the shards to return the top documents from each of the top ranking groups.
If we only want to return the highest scoring document per group we can return the top document id in the first step, merge results in the federator to retain the top K groups and then skip the second grouping step entirely.
QueryComponent: interim 'make it compile (somehow)' change (apache#228)
add SearchGroupsContainer (apache#230)
factor out SearchGroupsResultTransformer.serializeOneSearchGroup method (Christine)
Refactor transformToNative adding deserializeOneSearchGroup
increase GroupParams.GROUP_SKIP_DISTRIBUTED_SECOND use (see also 6bdf87)
Remove error logging in allowSkipSecondGroupingStep
Check that withinGroupSort is a prefix of groupSort
SkipSecondStepSearchGroupShardResponseProcessor.addSearchGroupToShards now leaves ShardDoc.fields null
factor out TopGroupsShardResponseProcessor.fillResultIds method
Add regression test group.main=true and group.format=simple
Improve GroupingSpecification validation adding validate() method
SkipSecondStepSearchResultResultTransformer.serializeOneSearchGroup tweaks
cpoerschke
pushed a commit
to cpoerschke/lucene-solr
that referenced
this pull request
Nov 22, 2019
…gas patch)
Summary:
In cases where we do grouping and ask for {{group.limit=1}} only it is possible to skip the second grouping step. In our test datasets it improved speed by around 40%.
Essentially, in the first grouping step each shard returns the top K groups based on the highest scoring document in each group. The top K groups from each shard are merged in the federator and in the second step we ask all the shards to return the top documents from each of the top ranking groups.
If we only want to return the highest scoring document per group we can return the top document id in the first step, merge results in the federator to retain the top K groups and then skip the second grouping step entirely.
QueryComponent: interim 'make it compile (somehow)' change (apache#228)
add SearchGroupsContainer (apache#230)
factor out SearchGroupsResultTransformer.serializeOneSearchGroup method (Christine)
Refactor transformToNative adding deserializeOneSearchGroup
increase GroupParams.GROUP_SKIP_DISTRIBUTED_SECOND use (see also 6bdf87)
Remove error logging in allowSkipSecondGroupingStep
Check that withinGroupSort is a prefix of groupSort
SkipSecondStepSearchGroupShardResponseProcessor.addSearchGroupToShards now leaves ShardDoc.fields null
factor out TopGroupsShardResponseProcessor.fillResultIds method
Add regression test group.main=true and group.format=simple
Improve GroupingSpecification validation adding validate() method
SkipSecondStepSearchResultResultTransformer.serializeOneSearchGroup tweaks
diegoceccarelli
pushed a commit
to diegoceccarelli/lucene-solr
that referenced
this pull request
Dec 4, 2019
…gas patch)
Summary:
In cases where we do grouping and ask for {{group.limit=1}} only it is possible to skip the second grouping step. In our test datasets it improved speed by around 40%.
Essentially, in the first grouping step each shard returns the top K groups based on the highest scoring document in each group. The top K groups from each shard are merged in the federator and in the second step we ask all the shards to return the top documents from each of the top ranking groups.
If we only want to return the highest scoring document per group we can return the top document id in the first step, merge results in the federator to retain the top K groups and then skip the second grouping step entirely.
QueryComponent: interim 'make it compile (somehow)' change (apache#228)
add SearchGroupsContainer (apache#230)
factor out SearchGroupsResultTransformer.serializeOneSearchGroup method (Christine)
Refactor transformToNative adding deserializeOneSearchGroup
increase GroupParams.GROUP_SKIP_DISTRIBUTED_SECOND use (see also 6bdf87)
Remove error logging in allowSkipSecondGroupingStep
Check that withinGroupSort is a prefix of groupSort
SkipSecondStepSearchGroupShardResponseProcessor.addSearchGroupToShards now leaves ShardDoc.fields null
factor out TopGroupsShardResponseProcessor.fillResultIds method
Add regression test group.main=true and group.format=simple
Improve GroupingSpecification validation adding validate() method
SkipSecondStepSearchResultResultTransformer.serializeOneSearchGroup tweaks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.