Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 2 Aug 2011 00:10:27 +0000 (UTC)
From: "Phillipe Ramalho (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1519447191.148.1312243827909.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1663956819.59.1300687385841.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (LUCENE-2979) Simplify configuration API of
 contrib Query Parser
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phillipe Ramalho updated LUCENE-2979:
-------------------------------------

    Attachment: LUCENE-2979_phillipe_ramalho_4_trunk.patch
                LUCENE-2979_phillipe_ramalho_4_3x.patch

Here is a patch that backports the new configuration API to 3.x. I did exactly as I described in my proposal and it seems to be working as expected. I changed the documentation as well (I hope I everything, can you double check that Adriano?).

I also created a simple example of how to use the new API in package.html and added to both 3.x and trunk.

Please, let me know if everything looks good and if I didn't break any API.

> Simplify configuration API of contrib Query Parser
> --------------------------------------------------
>
>                 Key: LUCENE-2979
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2979
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/other
>    Affects Versions: 2.9, 3.0
>            Reporter: Adriano Crestani
>            Assignee: Adriano Crestani
>              Labels: api-change, gsoc, gsoc2011, lucene-gsoc-11, mentor
>             Fix For: 3.4, 4.0
>
>         Attachments: LUCENE-2979_phillipe_ramalho_2.patch, LUCENE-2979_phillipe_ramalho_3.patch, LUCENE-2979_phillipe_ramalho_3.patch, LUCENE-2979_phillipe_ramalho_4_3x.patch, LUCENE-2979_phillipe_ramalho_4_trunk.patch, LUCENE-2979_phillipe_reamalho.patch
>
>
> The current configuration API is very complicated and inherit the concept used by Attribute API to store token information in token streams. However, the requirements for both (QP config and token stream) are not the same, so they shouldn't be using the same thing.
> I propose to simplify QP config and make it less scary for people intending to use contrib QP. The task is not difficult, it will just require a lot of code change and figure out the best way to do it. That's why it's a good candidate for a GSoC project.
> I would like to hear good proposals about how to make the API more friendly and less scaring :)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org