[
https://issues.apache.org/jira/browse/LUCENE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846719#action_12846719
]
Robert Muir commented on LUCENE-2323:
-------------------------------------
bq. it could be that I thought it was a really great idea at the time
my problem is not in the idea, but that its just unrealistic.
more realistic, lets say for the queryparsers would be, for example:
# moving the queryparsers together as i proposed here
# implementing some of the specialized ones with the new flexible queryparser
(LUCENE-1823)
# removing the now obselete specialized queryparsers.
# improving tests and general quality of the queryparsing package
At this point the code might be mature enough for an idea like yours.
I'm also realistic, and I know I probably cannot do much here except step 1, as
I'm not a queryparser expert.
But I can say there's at least a patch open for step 2, even if this patch
might not yet be ready.
So this seems like a realistic small step forward towards improving things.
The modularization idea won't cleanup contrib... some of it is hairy and that
needs to be done first.
> reorganize contrib modules
> --------------------------
>
> Key: LUCENE-2323
> URL: https://issues.apache.org/jira/browse/LUCENE-2323
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/*
> Reporter: Robert Muir
>
> it would be nice to reorganize contrib modules, so that they are bundled
> together by functionality.
> For example:
> * the wikipedia contrib is a tokenizer, i think really belongs in
> contrib/analyzers
> * there are two highlighters, i think could be one highlighters package.
> * there are many queryparsers and queries in different places in contrib
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
