[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042487#comment-17042487 ] Robert Muir commented on SOLR-599: -- Can the lightweight solrj client have lightweight *tests* too, using mocks instead of flaky tests that very slowly spin up multiple jetty servers? > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042143#comment-17042143
]
Andrzej Bialecki commented on SOLR-599:
---
{quote}aliases are not really supported in the http only client
{quote}
Is this really the case though? If you use {{CloudSolrClient}} with HTTP
{{ClusterStateProvider}} aliases are supported and are lazily refreshed in a
similar fashion like the cluster state.
> Lightweight SolrJ client
>
>
> Key: SOLR-599
> URL: https://issues.apache.org/jira/browse/SOLR-599
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrJ
>Reporter: Shalin Shekhar Mangar
>Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch,
> SOLR-599.patch
>
>
> SolrJ provides a SolrServer implementation backed by commons-httpclient which
> introduces many dependency jars (commons-codec, commons-io and
> commons-logging). Apart from that SolrJ also uses StAX API for XML parsing
> which introduces dependencies like stax-api, stax and stax-utils.
> This enhancement will add a SolrServer implementation backed by
> java.net.HttpUrlConnection and will use BinaryResponseParser as the default
> response parser. Using this basic implementation out of the box would require
> no dependencies on either commons-httpclient or StAX. The only dependency
> would be on solr-commons making this a very lightweight and distribution
> friendly Java client for Solr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041092#comment-17041092 ] Noble Paul commented on SOLR-599: - This can be documented and maybe a ticket can be created to fix this. Even if the user has all the dependencies in the classpath, if they choose to use the HTTP only client , it may have this shortcoming. So , it has nothing to do with dependencies > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041086#comment-17041086 ] Gus Heck commented on SOLR-599: --- It's fine if we have an additional client not supporting aliases, but aliases (for lots of reasons other than TRA's) are part of solr, so the "lightweight" client needs to be clear that it's not a full replacement for the zookeeper based solrj client then. Not supporting Aliases makes re-indexing scenarios difficult too. The swap out of a newly indexed collection will be much more prone to some clients getting the old data for a while, which means that consumers have to be coded to handle both old and new schema without error. I'm only bringing this stuff up because I was getting the impression that this was being viewed as a full featured alternative to the existing client. > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041069#comment-17041069
]
Noble Paul commented on SOLR-599:
-
aliases are not really supported in the http only client. Probably , you should
just {{touch}} all the relevant state.json files after the {{aliases.json}} is
modified
> Lightweight SolrJ client
>
>
> Key: SOLR-599
> URL: https://issues.apache.org/jira/browse/SOLR-599
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrJ
>Reporter: Shalin Shekhar Mangar
>Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch,
> SOLR-599.patch
>
>
> SolrJ provides a SolrServer implementation backed by commons-httpclient which
> introduces many dependency jars (commons-codec, commons-io and
> commons-logging). Apart from that SolrJ also uses StAX API for XML parsing
> which introduces dependencies like stax-api, stax and stax-utils.
> This enhancement will add a SolrServer implementation backed by
> java.net.HttpUrlConnection and will use BinaryResponseParser as the default
> response parser. Using this basic implementation out of the box would require
> no dependencies on either commons-httpclient or StAX. The only dependency
> would be on solr-commons making this a very lightweight and distribution
> friendly Java client for Solr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041063#comment-17041063 ] Gus Heck commented on SOLR-599: --- One case that could become troublesome for TRA's is servicing requests to the TRA where the oldest collection has become deleted (automatically). The request would find the collection in it's cached notion of the TRA but not in the cluster. That 404 needs to not kill the entirely valid query... so with lazy/optimistic comes handling of stale state errors and decisions about retries. > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041054#comment-17041054 ] Noble Paul commented on SOLR-599: - Optimistic caching works for `state.json` . The requests send the zk versions of the cached state.json files along with the requests. if the versions are wrong the nodes respond with an invalid cache message. The client then fetches fresh state and makes the request again > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041047#comment-17041047 ] Jan Høydahl commented on SOLR-599: -- Should be enough with optimistic, yes. Gus' concern I guess was that if things change in ZK before a request, then something could go wrong? I assume that the worst that can happen is that SolrJ sends updates to a dead node (in which case it will retry to another node) or to a non-leader (in which case a new state will be cached for the next request?). What do you mean could go wrong with aliases Gus? > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040942#comment-17040942 ] Noble Paul commented on SOLR-599: - A persistent connection does not make a lot of sense for a cluster with 100's of nodes. There is no guarantee that the node that the client is connected to will continue to be alive for long. In fact, there is no need for the client to be constantly up to date about the state of the cluster. It should make all requests optimistically > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040775#comment-17040775 ] Jan Høydahl commented on SOLR-599: -- I'm not sure, but with HTTP2 we could have Solr server side push a message to the client that state has changed, over the same persistent connection? > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040594#comment-17040594 ] Noble Paul commented on SOLR-599: - Today it's caching with a TTL. How else can we optimize it? > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040448#comment-17040448
]
Andrzej Bialecki commented on SOLR-599:
---
{{BaseHttpClusterProvider}} is still polling... or actually, caching the state
for up to 5 sec and then refreshing it on the next request. I'm not sure how we
could make it better just using HTTP.
> Lightweight SolrJ client
>
>
> Key: SOLR-599
> URL: https://issues.apache.org/jira/browse/SOLR-599
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrJ
>Reporter: Shalin Shekhar Mangar
>Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch,
> SOLR-599.patch
>
>
> SolrJ provides a SolrServer implementation backed by commons-httpclient which
> introduces many dependency jars (commons-codec, commons-io and
> commons-logging). Apart from that SolrJ also uses StAX API for XML parsing
> which introduces dependencies like stax-api, stax and stax-utils.
> This enhancement will add a SolrServer implementation backed by
> java.net.HttpUrlConnection and will use BinaryResponseParser as the default
> response parser. Using this basic implementation out of the box would require
> no dependencies on either commons-httpclient or StAX. The only dependency
> would be on solr-commons making this a very lightweight and distribution
> friendly Java client for Solr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[ https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040356#comment-17040356 ] Gus Heck commented on SOLR-599: --- Do those HTTP API's have a way to proactively advise the client of changes to aliases, available nodes etc? or do they require/conduct polling? Isn't one of the primary reasons we have zk because it allows the client to watch for changes? I've been meaning to look into this but keep getting distracted by other things so I better just mention it :). I remember having some difficulty with the http providers when the tests randomly selected them while I was working on TRAs, but they may have improved since then. > Lightweight SolrJ client > > > Key: SOLR-599 > URL: https://issues.apache.org/jira/browse/SOLR-599 > Project: Solr > Issue Type: Improvement > Components: clients - java, SolrJ >Reporter: Shalin Shekhar Mangar >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch, > SOLR-599.patch > > > SolrJ provides a SolrServer implementation backed by commons-httpclient which > introduces many dependency jars (commons-codec, commons-io and > commons-logging). Apart from that SolrJ also uses StAX API for XML parsing > which introduces dependencies like stax-api, stax and stax-utils. > This enhancement will add a SolrServer implementation backed by > java.net.HttpUrlConnection and will use BinaryResponseParser as the default > response parser. Using this basic implementation out of the box would require > no dependencies on either commons-httpclient or StAX. The only dependency > would be on solr-commons making this a very lightweight and distribution > friendly Java client for Solr. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040256#comment-17040256
]
Andrzej Bialecki commented on SOLR-599:
---
ZK dependencies can be avoided by using already existing HTTP-based
implementations of these APIs: {{ClusterStateProvider}}, {{NodeStateProvider}}
and not yet implemented (but relatively easy to do) {{DistribStateManager}}.
All these APIs were specifically created to isolate some areas of Solr from ZK.
{{CloudSolrClient}} can use these APIs to avoid using ZK APIs during runtime.
The way {{CloudSolrClient}} is implemented now it still does have a
compile-time ZK dependency but we could start from {{CloudSolrClient}} and
simplify it to only use the {{ClusterStateProvider}} API and its HTP
implementation.
> Lightweight SolrJ client
>
>
> Key: SOLR-599
> URL: https://issues.apache.org/jira/browse/SOLR-599
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrJ
>Reporter: Shalin Shekhar Mangar
>Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch,
> SOLR-599.patch
>
>
> SolrJ provides a SolrServer implementation backed by commons-httpclient which
> introduces many dependency jars (commons-codec, commons-io and
> commons-logging). Apart from that SolrJ also uses StAX API for XML parsing
> which introduces dependencies like stax-api, stax and stax-utils.
> This enhancement will add a SolrServer implementation backed by
> java.net.HttpUrlConnection and will use BinaryResponseParser as the default
> response parser. Using this basic implementation out of the box would require
> no dependencies on either commons-httpclient or StAX. The only dependency
> would be on solr-commons making this a very lightweight and distribution
> friendly Java client for Solr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
[jira] [Commented] (SOLR-599) Lightweight SolrJ client
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040183#comment-17040183
]
Jan Høydahl commented on SOLR-599:
--
We now have 29 dependencies:
{noformat}
commons-io-2.6.jar
commons-math3-3.6.1.jar
http2-client-9.4.24.v20191120.jar
http2-common-9.4.24.v20191120.jar
http2-hpack-9.4.24.v20191120.jar
http2-http-client-transport-9.4.24.v20191120.jar
httpclient-4.5.10.jar
httpcore-4.4.12.jar
httpmime-4.5.10.jar
jcl-over-slf4j-1.7.24.jar
jetty-alpn-client-9.4.24.v20191120.jar
jetty-alpn-java-client-9.4.24.v20191120.jar
jetty-client-9.4.24.v20191120.jar
jetty-http-9.4.24.v20191120.jar
jetty-io-9.4.24.v20191120.jar
jetty-util-9.4.24.v20191120.jar
netty-buffer-4.1.29.Final.jar
netty-codec-4.1.29.Final.jar
netty-common-4.1.29.Final.jar
netty-handler-4.1.29.Final.jar
netty-resolver-4.1.29.Final.jar
netty-transport-4.1.29.Final.jar
netty-transport-native-epoll-4.1.29.Final.jar
netty-transport-native-unix-common-4.1.29.Final.jar
slf4j-api-1.7.24.jar
stax2-api-3.1.4.jar
woodstox-core-asl-4.4.1.jar
zookeeper-3.5.5.jar
zookeeper-jute-3.5.5.jar{noformat}
See [mailing list thread "SolrJ has 29 compile-time
dependencies"|https://lists.apache.org/thread.html/r637d3a728102c262b3355e10c2b9a25731f7e7225d70f5dd87d56929%40%3Cdev.lucene.apache.org%3E]
for more discussion.
It has been suggested to create a new client for 9.0 based on Java's built-in
HTTP2 client, and without the Zookeeper dependencies. I guess that would let us
skip most of the other dependencies as well?
What about all the classes in {{o.a.s.common}} - many of those depend on
Zookeeper. But SolrJ code also depend on many of these such as {{common.util}}.
How to break it up so that we do not need to depend on all or nothing for SolrJ?
> Lightweight SolrJ client
>
>
> Key: SOLR-599
> URL: https://issues.apache.org/jira/browse/SOLR-599
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, SolrJ
>Reporter: Shalin Shekhar Mangar
>Assignee: Noble Paul
>Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-599-fix-for-SolrJ-on-GAE.patch, SOLR-599.patch,
> SOLR-599.patch
>
>
> SolrJ provides a SolrServer implementation backed by commons-httpclient which
> introduces many dependency jars (commons-codec, commons-io and
> commons-logging). Apart from that SolrJ also uses StAX API for XML parsing
> which introduces dependencies like stax-api, stax and stax-utils.
> This enhancement will add a SolrServer implementation backed by
> java.net.HttpUrlConnection and will use BinaryResponseParser as the default
> response parser. Using this basic implementation out of the box would require
> no dependencies on either commons-httpclient or StAX. The only dependency
> would be on solr-commons making this a very lightweight and distribution
> friendly Java client for Solr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
