[ 
https://issues.apache.org/jira/browse/SOLR-14712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Noble Paul updated SOLR-14712:
------------------------------
    Description: 
We should have a standard mechanism to make a request to the right replica/node 
across solr code.

This RPC mechanism assumes that
 * The RPC mechanism is HTTP
 * It is aware of all collections,shards & their topology etc
 * it knows how to route a request to the correct core

 This is agnostic of wire level formats ,Solr documents etc. That is a layer 
above this.

Anyone can use their own JSON parser or any other RPC wire level format on top 
of this

  was:
We should have a standard mechanism to make a request to the right replica/node 
across solr code.

This RPC mechanism assumes that
* The RPC mechanism is HTTP
* It is aware of all collections,shards & their topology etc
* it knows how to route a request to the correct core




 


> Standardize RPC calls in Solr
> -----------------------------
>
>                 Key: SOLR-14712
>                 URL: https://issues.apache.org/jira/browse/SOLR-14712
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should have a standard mechanism to make a request to the right 
> replica/node across solr code.
> This RPC mechanism assumes that
>  * The RPC mechanism is HTTP
>  * It is aware of all collections,shards & their topology etc
>  * it knows how to route a request to the correct core
>  This is agnostic of wire level formats ,Solr documents etc. That is a layer 
> above this.
> Anyone can use their own JSON parser or any other RPC wire level format on 
> top of this



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to