Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: veganjenny@gmail.com (jenny w)
Subject: [sup-talk] Amazon.com messages can't be added to index
Date: Sun, 14 Oct 2007 02:04:04 -0700	[thread overview]
Message-ID: <b1d95faa0710140204x2bfcfa9dt6489c66ec146f684@mail.gmail.com> (raw)
In-Reply-To: <20071014052003.GE17985@horacrux>

On 10/13/07, Kevin Mark <kevin.mark at verizon.net> wrote:
> It would be helpful to the list to show a portion of the actual error
> message(or all of it if its small) instead of a restatement of it. A
> restatement of an error message is rarely adequet to solve an error.


Okay, more info. I ended up running this under ruby-debug to see what
was going on.  It seems the problem I'm having is that Amazon.com
sends me messages with message_ids like:

    AAA-notification-70925, 4617.1234123412 at na-rte-app-5105.iad5.amazon.com

The space after the comma is what's throwing ferret off.

I don't know if it helps, but I noticed that if I try doing
@index.search("message_id:#{m.id}") ferret will find the doc. This
seems to be because Ferret is turning the string into a Boolean (as
opposed to Term) query.


  reply	other threads:[~2007-10-14  9:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14  3:32 jenny w
2007-10-14  5:20 ` Kevin Mark
2007-10-14  9:04   ` jenny w [this message]
2007-10-14 21:23     ` Christopher Warrington
2007-10-14 22:32       ` jenny w
2007-10-28  3:06         ` William Morgan
2008-02-22 15:46 Luis Villa
2008-02-22 16:25 ` Luis Villa
2008-02-25  5:10   ` William Morgan
2008-02-25 17:08     ` Christopher Warrington
2008-02-25 17:13       ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b1d95faa0710140204x2bfcfa9dt6489c66ec146f684@mail.gmail.com \
    --to=veganjenny@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox