Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asynchronous queries and updates in SOLR? #621

Open
jnioche opened this issue Oct 2, 2018 · 2 comments
Open

asynchronous queries and updates in SOLR? #621

jnioche opened this issue Oct 2, 2018 · 2 comments

Comments

@jnioche
Copy link
Contributor

jnioche commented Oct 2, 2018

Maybe https://github.com/inoio/solrs would be useful?

@jnioche
Copy link
Contributor Author

jnioche commented Jun 21, 2022

see https://solr.apache.org/guide/solr/latest/deployment-guide/solrj.html

ConcurrentUpdateHttp2SolrClient - just like ConcurrentUpdateSolrClient but using Http2SolrClient instead. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.

Not sure whether CloudSolrClient is asynchronous

[CloudSolrClient] (https://solr.apache.org/docs/9_0_0/solrj/org/apache/solr/client/solrj/impl/CloudSolrClient.html) - geared towards communicating with SolrCloud deployments. Uses already-recorded ZooKeeper state to discover and route requests to healthy Solr nodes.

@mvolikas
Copy link
Contributor

My understanding is the following:

  • ConcurrentUpdateHttp2SolrClient is not experimental in version 9.7.0 and seems promising for the StatusUpdater and Inderer bolts where it can batch updates without changing the way we submit documents.

  • Regarding querying in the spouts we could use the requestAsync of the Http2SolrClient with futures.

  • I'm not sure about the benefits of the CloudSolrClient, to be honest. The API seems to be synchronous from the caller's perspective. Additionally, since we currently have a single node (with multiple shards for the status collection) we will not use any of the automatic routing (e.g. load balancing requests across nodes) and failover (e.g. a node goes down) features.

Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants