[ 
https://issues.apache.org/jira/browse/SOLR-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041426#comment-18041426
 ] 

ASF subversion and git services commented on SOLR-18005:
--------------------------------------------------------

Commit a3b5af4e55fb7857efe1846474dfdaa502cde873 in solr's branch 
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a3b5af4e55f ]

SOLR-18005: ConcurrentUpdateJettySolrClient (#3885)

Renamed ConcurrentUpdateHttp2SolrClient to ConcurrentUpdateBaseSolrClient, made 
it abstract, and made a new ConcurrentUpdateJettySolrClient as the one 
implementation.  Moved logic from Http2SolrClient that was only related to this 
logic, over here.

* javadoc record: MissingDoclet didn't consider Java record

> Rename & move jetty based SolrClient code to its own package
> ------------------------------------------------------------
>
>                 Key: SOLR-18005
>                 URL: https://issues.apache.org/jira/browse/SOLR-18005
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrJ
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> (split off from SOLR-17161)
> SolrJ code depending on Jetty ought to be in a separate Java package.  
> Propose: {{org.apache.solr.client.solrj.jetty}}.  Classes in there should 
> generally have Jetty in the name, like ConcurrentUpdateJettySolrClient, 
> LBJettySolrClient, CloudJettySolrClient, HttpJettySolrClient.  This means not 
> just renames but sometimes splitting Jetty-ness out of other classes that 
> otherwise barely have any such dependency.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to