[
https://issues.apache.org/jira/browse/SOLR-16234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545898#comment-17545898
]
Jason Gerlowski commented on SOLR-16234:
----------------------------------------
JIRA really mangled your code snippet [~epugh] , so I'm having a bit of trouble
understanding your broader point: do you like the raw-request idea, or dislike
it, or land somewhere in between?
I agree that finding the right SolrJ request object can be tricky, which could
be an argument for adding "raw-request" capabilities*. But OTOH the snippet
you provided (and described as opaque and brittle) looks raw-request-y (SolrJ
user explicitly providing path, request body, etc.). Just trying to understand
your thoughts a little better.
[*] IMO "which-SolrJ-request-object-do-I-need-and-how-do-I-use-it" is a
documentation problem, not a code problem. The problem would disappear entirely
if the ref-guide had SolrJ snippets on ref-guide pages like "[Config
API|https://solr.apache.org/guide/solr/latest/configuration-guide/config-api.html]";,
for instance
> An API to make raw requests and responses to Solr
> --------------------------------------------------
>
> Key: SOLR-16234
> URL: https://issues.apache.org/jira/browse/SOLR-16234
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: clients - java
> Reporter: Noble Paul
> Priority: Major
>
> All Solr APIs are higher level APIs that deals with objects . We need a
> simple raw API for users who wish to interact with Solr without these Objects
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
