yeah there is a performance hit but that is expected. in my scenario i pass sometimes a few thousand using this method, but i pre-process my results since its a set. you will not have any issues if you are using POST with the uri length.
On Wed, Jun 26, 2019 at 3:02 PM Lucky Sharma <goku0...@gmail.com> wrote: > Thanks, Jagdish > But what if we need to perform search and filtering on those 1.5k doc > ids results, also for URI error, we can go with the POST approach, > and what if the data is not sharded. > > Regards, > Lucky Sharma > > On Thu, Jun 27, 2019 at 12:28 AM jai dutt <ghost.ridder2...@gmail.com> > wrote: > > > > 1. No Solr is not for id search. rdms a better option. > > 2. Yes correct it going to impact query performance. And you may got > > large uri error. > > 3 ya you can pass ids internally by writing any custom parser.or divide > > data into different shard. > > > > > > > > On Thu, 27 Jun, 2019, 12:01 AM Lucky Sharma, <goku0...@gmail.com> wrote: > > > > > Hi all, > > > > > > What we are doing is, we will be having a set of unique Ids of solr > > > document at max 1500, we need to run faceting and sorting among them. > > > there is no direct search involved. > > > It's a head-on search since we already know the document unique keys > > > beforehand. > > > > > > 1. Is Solr a better use case for such kind of problem? > > > 2. Since we will be passing 1500 unique document ids, As per my > > > understanding it will impact query tree as it will grow bigger. Will > > > there be any other impacts? > > > 3. Is it wise to use or solve the situation in this way? > > > > > > > > > -- > > > Warm Regards, > > > > > > Lucky Sharma > > > > > > > -- > Warm Regards, > > Lucky Sharma > Contact No :+91 9821559918 >
