Along similar lines :
assuming that i have 2 indexes in the same box , say at :
/home/abc/data/index1 and /home/abc/data/index2,
and i want the results from both the indexes when i do a search - then how
should this be 'optimally' designed - basically these are different Solr
homes and i want the results to be clearly demarcated as coming from 2
different sources.
-Venkat
On 9/20/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
>
> On Thu, 20 Sep 2007 10:21:39 +0800
> "Jarvis" <[EMAIL PROTECTED]> wrote:
>
> > What you say is done by hadoop that support Hardware FailurećData
> > Replication and some else .
> > If we want to implement such a good system by ourselves without
> HDFS
> > but Solr , it's a very very complex work I think. :)
> > I just want to know whether there is a component existed can do
> the
> > distributed search based on Solr.
>
> Thanks for the info.
>
> Risking starting up a flame war (which is not my intention :) ), what
> design reasons / features are there in Solr but not in hadoop/nutch that
> would make it compelling to use solr instead of h/n ?
>
> I know, each case is
> different.... the feeling i got from a shortish read into h/n was that H/N
> is
> geared towards webpage indexing, crawling,etc. But possibly i'm missing
> something...
>
> Where Solr is , from my point of view, far more flexible. In which case,
> maybe
> porting HDFS into Solr to add all this clustering / map/reduce options...
>
> thanks for your time and insights :)
> B
> _________________________
> {Beto|Norberto|Numard} Meijome
>
> Windows caters to everyone as though they are idiots. UNIX makes no such
> assumption. It assumes you know what you are doing, and presents the
> challenge
> of figuring it out for yourself if you don't.
>
> I speak for myself, not my employer. Contents may be hot. Slippery when
> wet.
> Reading disclaimers makes you go blind. Writing them is worse. You have
> been
> Warned.
>
--
