[
https://issues.apache.org/jira/browse/SOLR-16234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550466#comment-17550466
]
Jason Gerlowski commented on SOLR-16234:
----------------------------------------
bq. For sake of efficiency and simplicity
Efficiency I guess makes sense, though I'm not familiar with the specific SolrJ
efficiency problems you're referring to, so I'm just taking your word for it to
some extent.
But simplicity? Stepping away an interface that abstracts away the API details
and instead having to build your own path/query-params/request-body....well
that seems like a step backwards in terms of "simplicity" in my opinion?
I guess the root of my concern is that it feels like we're hacking around a
problem here, instead of addressing it in earnest. SolrJ is GC-inefficient or
memory-inefficient? OK, well let's talk about and fix that. Not put a
band-aid on it that'll only help some users, some of the time, at some other
cost (writing their own serde code, additional pain on upgrades, etc.)
> 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
> Assignee: Noble Paul
> Priority: Major
> Fix For: 9.1
>
>
> 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]
