lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phillipe Ramalho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-2979) Simplify configuration API of contrib Query Parser
Date Fri, 26 Aug 2011 05:57:29 GMT

     [ 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_5_3x.patch

Creating a junit for attributes was a good idea, I was able to find many problems. I spent
the last three weeks working on them and reviewing the code. I think this is the last patch
for this jira, it should be done now.

> 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_ramalho_5_3x.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


Mime
View raw message