This issue is really providing yet another convenience method to perform CRUD operations.
Create & Update Operations:
UpdateResponse resp = solrServer.add(SolrInputDocument);
UpdateResponse resp = solrServer.add(Collection<SolrInputDocument>);
These methods don't necessarily need to align to the various REST HTTP method semantics. The "add" action will perform a create or update clobbering the document already in place with the ability to perform an atomic update operation which will perform a merge with the document already in the index.
UpdateResponse resp = solrServer.deleteById(String id);
UpdateResponse resp = solrServer.deleteById(Collection<String> id);
UpdateResponse resp = solrServer.deleteByQuery(String query);
QueryResponse resp = solrServer.query(SolrParams);
As you can see the delete operation allows you to delete given a specific id or delete by a query, whereas the retrieval only gives you query access. To be consistent this ticket should provide the ability to retrieve by id as a convenience to developers using the SolrJ API (not to mention the additional benefits they will get from the RealTimeGetHandler).