[
https://issues.apache.org/jira/browse/LUCENE-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011721#comment-13011721
]
Adriano Crestani commented on LUCENE-2979:
------------------------------------------
Hi Phillip,
I like your idea, similiar to the one I have, but I was planning to use enum,
however, after spent some time thinking, I can't see how I can use generic the
way you described only using enum. So go ahead with your idea and create a
proposal ;)
Don't forget to describe how you plan make the old and new API work together.
> 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: contrib/*
> Affects Versions: 2.9, 3.0
> Reporter: Adriano Crestani
> Assignee: Adriano Crestani
> Labels: api-change, gsoc, gsoc2011, lucene-gsoc-11, mentor
> Fix For: 3.2, 4.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
