Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of gento0nz@gmail.com designates
 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <tencent_04844E4B51A3841309BD7B4B@qq.com>
References: <tencent_04844E4B51A3841309BD7B4B@qq.com>
Date: Mon, 12 Nov 2012 21:52:24 +1300
Message-ID: 
 <CACQS3vRWDEjO_mKfrK5N0Y8jB3rXnBOjpLBZfUUuSTLHF=qrXw@mail.gmail.com>
Subject: Re: Why QueryParser isn't in API?
From: Chris Male <gento0nz@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=047d7b6d911699455404ce486b1f

--047d7b6d911699455404ce486b1f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

All the QueryParsers were consolidated into their own module in Lucene 4.0.


http://lucene.apache.org/core/4_0_0/queryparser/index.html


On Mon, Nov 12, 2012 at 6:16 PM, =E4=BD=99=E9=9D=96=E6=AF=85 <502437499@qq.=
com> wrote:

> I'm a new Lucene programmer. I want to know why the class of QueryParser
>  didn't find in api. And a simple example in docs still used the class.
> And are there
>  anthor methods to replace it. Thx!
>
>         Harry Yu


--=20
Chris Male | Open Source Search Developer | elasticsearch |
www.e<http://www.dutchworks.nl>
lasticsearch.com

--047d7b6d911699455404ce486b1f--