@Shrikanth: how do you manage multiple redundant configurations(isn' it?) ?
I thought indexes would be separate when fields aren't shared. I don't need
to import any data/ or re-indexing, if those are the only benefits for
separate collections.  I just index when a request comes/ new item is added
to DB.


On Wed, Oct 16, 2013 at 4:12 PM, shrikanth k <jconsult.s...@gmail.com>wrote:

> Hi,
>
>     Please refer below link for clarification on fields having null value.
>
>
> http://stackoverflow.com/questions/7332122/solr-what-are-the-default-values-for-fields-which-does-not-have-a-default-value
>
> logically it is better to have different collections for different domain
> data. Having 2 collections will improve the overall performances.
>
> Currently am holding 2 collections for different domain data. It eases
> importing data and re-indexing.
>
>
> regards,
> Shrikanth
>
>
>
> On Wed, Oct 16, 2013 at 3:48 PM, user 01 <user...@gmail.com> wrote:
>
> > Can some expert users please leave a comment on this ?
> >
> >
> > On Sun, Oct 6, 2013 at 2:54 AM, user 01 <user...@gmail.com> wrote:
> >
> > >  Using a single node Solr instance, I need to search for, lets say,
> > > electronics items & grocery items. But I never want to search both of
> > them
> > > together. When I search for electrnoics I don't expect a grocery item
> > ever
> > > & vice versa.
> > >
> > > Should I be defining both these document types within a single
> schema.xml
> > > or should I use different collection for each of these two(maintaining
> > > separate schema.xml & solrconfig.xml for each of two) ?
> > >
> > > I believe that if I add both to a single collection, without sharing
> > > fields among these two document types, I should be equally good as
> > > separating them in two collection(in terms of performance & all), as
> > their
> > > indexes/filter caches would be totally independent of each other when
> > they
> > > don't share fields?
> > >
> > >
> > > Also posted at SO: http://stackoverflow.com/q/19202882/530153
> > >
> >
>
>
>
> --
>

Reply via email to