Erick, related that I noticed that a lot of times, a developer would need an intermediate API that will proxy the Search UI requests to Solr.
Of course there are scenarios where is necessary to build this intermediate API ( for example if you customise how the results must be processed after Solr returns them) . But sometimes it can happen a straightforward communication from the UI to Solr using the REST endpoints provided . In your opinion, does make any sense to provide the intermediate Search API in simple use cases as well ? Doing that, aren't we introducing scalability issues/ delay in query time ? I always thought the intermediate Rest API to be necessary, but day by day, Solr REST API are becoming more and more complete. To refer to the the user mail, maybe he can simply use Solr REST endpoints. But what about production environments ? Cheers 2015-06-24 2:18 GMT+01:00 Erick Erickson <erickerick...@gmail.com>: > First, the Velocity UI was never intended to be a user-facing application, > if > for no other reason than it has direct access to Solr. And I can delete > all the > docs in the collection, delete collections, create new collections and > all manner > of other really bad stuff. > > So almost _every_ application has its own UI for search. > > You don't need to worry in the least about the Solr code base. You > shouldn't > have to care. All you need to do is send HTTP requests to Solr and deal > with > the response. > > For instance, try these two commands from a browser: > http://sever:port/solr/collection/query?q=*:* > (that's star colon star in case your e-mail makes the colon just a bold). > http://sever:port/solr/collection/select?q=*:* > > You should see a JSON and XML response packet. _That's_ all you > really have to deal with. The rest of theUI has nothing to do with > Solr and everything to do with your UI skills, you "merely" have to parse > the response and display it pleasingly. > > If you don't want to curl the commands or use your own HTTP client, you > can use SolrJ to query Solr and not have to parse the response because > there are a bunch of helper methods that make navigating the response > easier, google "solrj query example" and you'll see a bunch of examples. Be > a little careful to make sure the example you use is compatible with your > Solr version. > > HTH, > Erick > > On Tue, Jun 23, 2015 at 5:20 PM, Paden <rumsey...@gmail.com> wrote: > > Hello, > > > > I'm trying to custom build my own Solr interface in Visual Studios > instead > > of using/modifying the original Velocity interface. I'm mostly doing > this as > > a learning exercise for building UI that's why I'm opting out of using > it. > > > > The problem is I'm pretty new and not sure where to begin. Most of the > posts > > I've seen end in people opting to modify the default UI. Are there any > good > > links to tutorials or good Solr classes I should look at as I'm trying to > > build this UI? > > > > This interface isn't to replace the Solr Admin page, it's simply to > handle > > the querying of the indexed documents that I have. > > > > If this seems more an "exercise in futility" (due to vast amounts of code > > that needs written or whatnot) then please let me know. I don't really > have > > any reason to believe it should be but I've been wrong before. > > > > Thanks in advance > > > > > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Creating-A-User-Interface-On-Top-of-Solr-tp4213541.html > > Sent from the Solr - User mailing list archive at Nabble.com. > -- -------------------------- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
