by default, each core has its own data (and index) you *could*
configure it to share the same data. The catch is you would need to
be careful that only one core is writing to the index . It is
potentially useful in some rare cases...
On May 1, 2008, at 1:14 AM, Norskog, Lance wrote:
I
I think I meant: this writeup implies to me that two cores could share
the same "default" index. I don't see how this would work, or be useful.
Thanks,
Lance Norskog
-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 30, 2008 9:30 PM
To: solr-user@l
On Apr 30, 2008, at 11:52 PM, Lance Norskog wrote:
The MultiCore writeup on the Wiki (http://wiki.apache.org/solr/MultiCore
)
says:
...
Configuration->core->dataDir
The data directory for a given core. (optional)
How can a core not have its own dataDir? What happens if this is not
s
The MultiCore writeup on the Wiki (http://wiki.apache.org/solr/MultiCore)
says:
...
Configuration->core->dataDir
The data directory for a given core. (optional)
How can a core not have its own dataDir? What happens if this is not set?
Cheers,
Lance Norskog
I have an index of about 3,000,000 products and about 8500
customers. Each customers has access to about 50 to about 500,000 of
the products.
Our current method was using a bitset in the filter. So, for each
customer, they have a bitset in the cache. For each docId that they
have access to, t
On 30-Apr-08, at 5:31 PM, Kevin Osborn wrote:
I have an index of about 3,000,000 products and about 8500
customers. Each customers has access to about 50 to about 500,000 of
the products.
Our current method was using a bitset in the filter. So, for each
customer, they have a bitset in th
I have an index of about 3,000,000 products and about 8500 customers. Each
customers has access to about 50 to about 500,000 of the products.
Our current method was using a bitset in the filter. So, for each customer,
they have a bitset in the cache. For each docId that they have access to, the
Hmmm, if there is a bug, odds are it's due to multicore stuff -
probably nothing else has touched core stuff like that recently.
Can you reproduce (or rather help others to reproduce) with the
solr/example setup?
-Yonik
On Wed, Apr 30, 2008 at 5:39 PM, Matthew Runo <[EMAIL PROTECTED]> wrote:
> H
Hello!
In using the SVN head version of Solr, I've found that recently we
started getting multiple open SegmentReaders, all registered... etc..
Any ideas why this would happen? They don't go away unless the server
is restarted, and don't go away with commits, etc. In fact, commits
seem to
I agree with you Jerome. It seems to me that the SolrCore.execute() should
log at DEBUG level (aka "FINE" in JUL parlance), not INFO. I too don't want
to raise the log level to WARN which would throw out the baby with the bath
water. For now, I'm just going to modify SolrCore line 958 since I'm
10 matches
Mail list logo