I have implemented a NoSQL key/value DB where I index the value field needed 
for retrieval plus the key value to get back the DB record when searching and 
it works pretty well.
I use Lucene but you can most probably do the same with SOLR.
Best wishes 

Envoyé de mon iPhone

> Le 12 août 2017 à 21:06, Leonardo Perez Pulido <leoperezpul...@gmail.com> a 
> écrit :
> The main reason to chose Solr is the capacity of it has of return results
> sorted by relevance. Solr returns documents in ranked order based on how
> relevant each document is to the user's query.
> Solr isn't a database, although it can 'store' data.
> Regards.
>> On Sat, Aug 12, 2017 at 2:27 PM, Dave <hastings.recurs...@gmail.com> wrote:
>> Personally I say use a rdbms for data storage, it's what it's for. Solr is
>> for search and retrieve and the expense of possible loss of all data, in
>> which case you rebuild it.
>>> On Aug 12, 2017, at 11:26 AM, Muwonge Ronald <ssed...@gmail.com> wrote:
>>> Hi Solr can use mongodb for storage and you can play with the data as it
>>> grows depending on your data goals.Ease of learning doesn't mean
>>> happiness.I recommend you use both for serious projects that won't
>> collapse
>>> soon.
>>> Ronny
>>>> On 5 Aug 2017 02:16, "Francesco Viscomi" <fvisc...@gmail.com> wrote:
>>>> Hi all,
>>>> why i have to choose solr if mongoDb is easier to learn and to use?
>>>> Both are NoSql database, is there a good reason to chose solr and not
>>>> mongoDb?
>>>> thanks really much
>>>> --
>>>> Ing. Viscomi Francesco

Reply via email to