Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 13531 invoked from network); 1 Jan 2010 18:34:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jan 2010 18:34:31 -0000 Received: (qmail 94882 invoked by uid 500); 1 Jan 2010 18:34:31 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 94856 invoked by uid 500); 1 Jan 2010 18:34:31 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 94846 invoked by uid 99); 1 Jan 2010 18:34:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jan 2010 18:34:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hirsch.dick@gmail.com designates 209.85.218.210 as permitted sender) Received: from [209.85.218.210] (HELO mail-bw0-f210.google.com) (209.85.218.210) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jan 2010 18:34:22 +0000 Received: by bwz2 with SMTP id 2so7607651bwz.20 for ; Fri, 01 Jan 2010 10:34:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=+DUMFZ/BGtzXN6oX5kcTIaVignPIeYxzN1rJ4YWR+Os=; b=HYBIKWv88NV6p2kAx1OscShSRaaii4dniS+J/vM6pY2p4YMDe1IqeRbJlcsds8PAm2 ku42q4/Clo/GTaj9OkHC3kUKLIqriC3q2OLqpT9jyfrcznfkQUWo5L8XBLA4TemcMtFS hNJbmKyRMnKoczDZiwYt0VojDYZj6Dromm88U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=CniubTu0XgRkdBfYpIYGbLhC4/LLZW8aDNMuqBRhyTRnpFAJ19unBpP6CN//mQCtL3 VWjHMmDEvSDIdl99/By7vkq7avo412rmWmy1KXDxJvCz14PUtQKIwXDq2ZXMwC6DFMzf ULzMu+GgpIpd04jde3AhBKpaO9yxZYojJQS3A= MIME-Version: 1.0 Received: by 10.204.33.139 with SMTP id h11mr3954402bkd.149.1262370839022; Fri, 01 Jan 2010 10:33:59 -0800 (PST) In-Reply-To: <68f4a0e81001010941v2fcd9b0i6ddad5ec323f4025@mail.gmail.com> References: <68f4a0e81001010941v2fcd9b0i6ddad5ec323f4025@mail.gmail.com> Date: Fri, 1 Jan 2010 19:33:59 +0100 Message-ID: Subject: Re: Search questions From: Richard Hirsch To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Jan 1, 2010 at 6:41 PM, Ethan Jewett wrote: > I'm testing out the search functionality a bit and I've got a couple > of questions: Are you thinking of adding search to the new api indirectly - which I prefer- or directly with a "search" method? > > 1. Search doesn't appear to be working on > http://esmecloudserverapache.dickhirsch.staxapps.net/ =A0Or rather, it's > working, but it only has messages in the index from around Dec 15th > and 16th. It seems to work fine when I build locally. Probably a local problem. I haven't tried search on the stax instance for a while. If desired, I could restart the server. > > 2. It looks like search filters messages by people I follow. When I > follow a new user, their messages start showing up in my search. When > I unfollow, those messages no longer show up in my search. Was this by > design? Would people be open to at least allowing an option to search > across all messages I have *access* to (by pool), rather than just > those of people I follow? The search functionality was conceived before we started pools. Thus, pools weren't include back then. I'd like to think that search in pool would be useful. What about searching across all "my" pools or a certain pool? > > 3. I'm thinking of using search in a way where I would want to search > *only* based on tags and *not* on the message text itself. Is this > currently possible? If not, can we set it up? Look here for the current search implementation: http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/main/scala/org= /apache/esme/model/Message.scala?view=3Dmarkup - starting on line 148 > > I'll be looking into this further on my own, but any pointers or > answers would be much appreciated. > > Ethan >