On Mon, 21 Oct 2013, Shawn Grant wrote:
ok, thx. My fault, I was on an older version and was going off the
changelog... should have just checked the new version.
Did that make its way in as part of the change to the namespace handling?
I don't know. It most likely came by way of appearing in Lucene proper.
Andi..
--
From
pylucene-dev-return-2190-apmail-lucene-pylucene-dev-archive=lucene.apache....@lucene.apache.org
Fri Oct 18 22:26:09 2013
Return-Path:
<pylucene-dev-return-2190-apmail-lucene-pylucene-dev-archive=lucene.apache....@lucene.apache.org>
X-Original-To: apmail-lucene-pylucene-dev-arch...@minotaur.apache.org
Delivered-To: apmail-lucene-pylucene-dev-arch...@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id DEBC810EF1
for <apmail-lucene-pylucene-dev-arch...@minotaur.apache.org>; Fri, 18
Oct 2013 22:26:09 +0000 (UTC)
Received: (qmail 30372 invoked by uid 500); 18 Oct 2013 22:26:09 -0000
Delivered-To: apmail-lucene-pylucene-dev-arch...@lucene.apache.org
Received: (qmail 30320 invoked by uid 500); 18 Oct 2013 22:26:09 -0000
Mailing-List: contact pylucene-dev-h...@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:pylucene-dev-h...@lucene.apache.org>
List-Unsubscribe: <mailto:pylucene-dev-unsubscr...@lucene.apache.org>
List-Post: <mailto:pylucene-dev@lucene.apache.org>
List-Id: <pylucene-dev.lucene.apache.org>
Reply-To: pylucene-dev@lucene.apache.org
Delivered-To: mailing list pylucene-dev@lucene.apache.org
Received: (qmail 30312 invoked by uid 99); 18 Oct 2013 22:26:09 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 22:26:09 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
spf.trusted-forwarder.org)
Received: from [50.0.193.30] (HELO ovaltofu.org) (50.0.193.30)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 22:26:02 +0000
Received: from [192.168.22.15] ([216.239.55.199])
(authenticated bits=0)
by ovaltofu.org (8.14.4/8.14.4) with ESMTP id r9IMPatP003936
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <pylucene-dev@lucene.apache.org>; Fri, 18 Oct 2013 15:25:39 -0700
(PDT)
Date: Fri, 18 Oct 2013 15:25:34 -0700 (PDT)
From: Andi Vajda <va...@apache.org>
X-X-Sender: vajda@yuzu.local
Reply-To: Andi Vajda <va...@apache.org>
To: pylucene-dev@lucene.apache.org
Subject: Re: complex phrase parsing
In-Reply-To: <5261a6c8.7000...@orcatec.com>
Message-ID: <alpine.OSX.2.01.1310181523190.589@yuzu.local>
References: <5261a6c8.7000...@orcatec.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Checked: Checked by ClamAV on apache.org
On Fri, 18 Oct 2013, Shawn Grant wrote:
I don't see that pylucene has a wrapper for the ComplexPhraseQueryParser...
am I wrong?
What version of pylucene are you referring to ?
It seems to be available in 4.4.0:
>>> from lucene import initVM
>>> initVM()
<jcc.JCCEnv object at 0x10029c0f0>
>>> from org.apache.lucene.queryparser.complexPhrase import
ComplexPhraseQueryParser
>>> ComplexPhraseQueryParser
<type 'ComplexPhraseQueryParser'>
Andi..
ps: please, subscribe to the list so that your messages don't have to be
moderated in. Thanks.
