Thanks Gora for your response. The main reason for trying to get search and grouping run outside the context of Solr is to avoid the load on Solr server. Using a Solr client API will consume resources on the Solr server itself. Please correct me if I'm wrong.
If it is possible to directly read an index from the EBSvolume and perform a search and grouping on AWS Lambda using Lucene/Solr API then the load on the Solr server will not increase. I found Lucene APIs not supporting non-docValue fields for grouping. Best, Modassar On Tue, Jul 20, 2021 at 4:00 PM Gora Mohanty <g...@mimirtech.com> wrote: > On Tue, 20 Jul 2021 at 15:05, Modassar Ather <modather1...@gmail.com> > wrote: > > > Hi, > > > > I have a requirement of simple search and grouping of the result on the > > index created using Solr-6.5.1 spread across 12 shards on a server > outside > > Solr context. > > These searches can run on AWS Lambda using its resources to minimise the > > load on the main Solr server with the index EBS volume attached to it. > > > > I am trying to find the solution using either of the following ways: > > > > - By directly being able to call Solr APIs for searches and grouping > on > > AWS Lambda. > > > > This should be possible. You will need to use one of the Solr client APIs, > installed outside of Lambda, and call the APIs from your Lambda functions. > Please see https://solr.apache.org/guide/8_9/client-apis.html > > > > - By installing Solr on AWS Lambda where the same index can be > attached > > and used for searching and grouping. > > > > Installing Solr on Lambda is probably not even possible, and certainly > inadvisable. > > Regards, > Gora >
