Just a thought: If your users can send updates and you can't trust them, how can you keep them from deleting all your data?
I would consider using a servlet filter to inspect the request. That would probably be non-trivial if you plan to accept javabin requests as well. Michael Della Bitta Applications Developer o: +1 646 532 3062 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions <https://twitter.com/Appinions> | g+: plus.google.com/appinions<https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts> w: appinions.com <http://www.appinions.com/> On Thu, May 22, 2014 at 6:36 AM, Furkan KAMACI <furkankam...@gmail.com>wrote: > Hi All; > > I've designed a system that allows people to use a search service from > SolrCloud. However I think that I should disable "commit" option for people > to avoid performance issues (many users can send commit requests and this > may cause to performance issues). I'll configure solr config file with > autocommit and I'll not let people to commit individually. > > I've done some implementation for it and people can not send commit request > by GET as like: > > localhost:8983/solr/update*?commit=true* > > and they can not use: > > HttpSolrServer solrServer = new HttpSolrServer("http://localhost:8983/solr > "); > solrServer*.commit();* > > I think that there is another way to send a commit request to Solr. It is > something like: > > {"add":{ "doc":{"id":"change.me","title":"change.me > "},"boost":1.0,"overwrite":true,"*commitWithin*":1000}} > > So, I want to stop that usage and my current implementation does not > provide it. > > My question is that: Is there anyway I can close the commit option for Solr > from "clients"/"outside the world of Solr" and manage that option only via > solr config? > > Thanks; > Furkan KAMACI >
