Our Solr use consists of several rather different data types, some of
which have one-to-many relationships with other types. We don't need
to do any searching of quite the kind you describe, but I have an idea
about it, depending on what you need to do with the book data. It is
rather hacky, but
We tried this architecture for our initial rollout of Solr/Lucene to
our production application. We ran into a problem with it, which may
or may not apply to you. Our production software servers all are
monitored for uptime by a daemon which pings them periodically and
restarts them if a response
you?
> It sounds like something that could work quite well for me too, but I
> would be a little worried that a commit could time out, and a unique
> value could be lost for that user.
>
> Thank you
> Alec
>
> On Feb 13, 2008, at 1:10 PM, Rachel McConnell wrote:
>
> >
We do something similar in a different context. I don't know if our
way is necessarily better, but it would work like this:
1. add a field to campaign called something like enteredUsers
2. once a user adds a campaign, update the campaign, adding a value
unique to that user to enteredUsers
3. the
On 2/4/08, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Feb 4, 2008 2:20 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote:
> > > If you are running snapshooter asynchronously, this would be the cause.
> > > It's designed to be run from solr (via a postCommit o
On 2/4/08, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Feb 4, 2008 1:48 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote:
> > On 2/4/08, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> > > On Feb 4, 2008 1:15 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote:
>
On 2/4/08, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Feb 4, 2008 1:15 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote:
> > We are using Solr's replication scripts. They are set to run every 20
> > minutes, via a cron job on the slave servers. Any further usef
er adding some
> documents but before the duplicates have been removed. Are you using
> Solr's replication scripts?
>
> -Yonik
>
> On Feb 1, 2008 6:01 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote:
> > We have just started seeing an intermittent problem in our producti
We have just started seeing an intermittent problem in our production
Solr instances, where the same document is returned twice in one
request. Most of the content of the response consists of duplicates.
It's not consistent; maybe 1/3 of the time this is happening and the
rest of the time, one ret
Thanks Hoss, so then it's actually the same values as returned in the
query response header, e.g. (JSON format):
{"responseHeader":{"status":0,"QTime":209},"response":{"numFound":2574,
... (omitted)
thx,
Rachel
On 1/28/08, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> : [10:58:26.507] /select
>
Hello all,
I'm not sure if this is a Solr question, but any pointers would be
helpful. I am seeing this kind of thing in the stdout logs (I believe
it to be entirely normal):
[10:58:26.507] /select
qt=relatedinstructables&q=music%0awall%0amount%0aguitar%0adiy%0astand%0amusicianhome+NOT+E7Z1HY8HQ
11 matches
Mail list logo
