From dev-return-321327-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Mon May 7 04:15:11 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 06DF3180674 for ; Mon, 7 May 2018 04:15:10 +0200 (CEST) Received: (qmail 88995 invoked by uid 500); 7 May 2018 02:15:04 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 88981 invoked by uid 99); 7 May 2018 02:15:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2018 02:15:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 36098C208A for ; Mon, 7 May 2018 02:15:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qRfnrWgrs73o for ; Mon, 7 May 2018 02:15:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id BAD3D5F485 for ; Mon, 7 May 2018 02:15:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8066DE12C2 for ; Mon, 7 May 2018 02:15:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2019021296 for ; Mon, 7 May 2018 02:15:00 +0000 (UTC) Date: Mon, 7 May 2018 02:15:00 +0000 (UTC) From: "Mark Miller (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-12297) Create a good SolrClient for SolrCloud paving the way for async requests, HTTP2, multiplexing, and the latest & greatest Jetty features. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-12297?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1646= 5363#comment-16465363 ]=20 Mark Miller commented on SOLR-12297: ------------------------------------ I'm sure that was for some special case. Http2 is never going to be a stron= g enough wind for a Java version change in the project. It=C2=A0turns out, = as mentioned above, we don't need Java 9 for good out of the box SSL or pro= tocol negotiation anyway though. I've got most of this working. The main things to finish are a few places w= here low level Apache HttpClient has been used, as well as stuff that uses = HttpClientUtil stuff to do advanced configuration or callback injection. Mo= st=C2=A0things and tests=C2=A0are working though. I'm not putting that in any time soon though. I'll push that to a branch an= d when the new client is cleaned up and a little nicer, focus on putting th= at in first. Then over time we can bring in the rest of the branch. > Create a good SolrClient for SolrCloud paving the way for async requests,= HTTP2, multiplexing, and the latest & greatest Jetty features. > -------------------------------------------------------------------------= --------------------------------------------------------------- > > Key: SOLR-12297 > URL: https://issues.apache.org/jira/browse/SOLR-12297 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public)=20 > Reporter: Mark Miller > Assignee: Mark Miller > Priority: Major > > Blocking or async support as well as HTTP2 compatible with multiplexing. > Once it supports enough and is stable, replace internal usage, allowing a= sync, and eventually move to HTTP2 connector and allow multiplexing. Could = support HTTP1.1 and HTTP2 on different ports depending on state of the worl= d then. > The goal of the client itself is to work against HTTP1.1 or HTTP2 with mi= nimal or no code path differences and the same for async requests (should i= nitially work for both 1.1 and 2 and share majority of code). > The client should also be able to replace HttpSolrClient and plug into th= e other clients the same way. > I doubt it would make sense to keep ConcurrentUpdateSolrClient eventually= though. > I evaluated some clients and while there are a few options, I went with J= etty's HttpClient. It's more mature than Apache HttpClient's support (in 5 = beta) and we would have to update to a new API for Apache HttpClient anyway= . > Meanwhile, the Jetty guys have been very supportive of helping Solr with = any issues and I like having the client and server from the same project. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org