You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Grant Ingersoll <gs...@apache.org> on 2008/04/17 15:35:39 UTC
Back Compatibility of Contrib. was Re: [jira] Commented: (LUCENE-1142) Updated Snowball package
Do we require the contrib to adhere to the same back compatibility
rules as trunk? I don't know that it has been established.
Thoughts? Analysis is a pretty tricky one, as compared to the other
packages.
On Apr 1, 2008, at 8:32 AM, Karl Wettin (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/LUCENE-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584119
> #action_12584119 ]
>
> Karl Wettin commented on LUCENE-1142:
> -------------------------------------
>
> I propose for this patch to be included in Lucene 3.0.0 (3.0.1?)
>
>
>> Updated Snowball package
>> ------------------------
>>
>> Key: LUCENE-1142
>> URL: https://issues.apache.org/jira/browse/LUCENE-1142
>> Project: Lucene - Java
>> Issue Type: Improvement
>> Components: Analysis
>> Reporter: Karl Wettin
>> Priority: Minor
>> Attachments: snowball.tartarus.txt
>>
>>
>> Updated Snowball contrib package
>> * New org.tartarus.snowball java package with patched
>> SnowballProgram to be abstract to avoid using reflection.
>> * Introducing Hungarian, Turkish and Romanian stemmers
>> * Introducing constructor SnowballFilter(SnowballProgram)
>> It is possible there have been some changes made to the some of
>> there stemmer algorithms between this patch and the current SVN
>> trunk of Lucene, an index might thus not be compatible with new
>> stemmers!
>> The API is backwards compatibile and the test pass.
>
> --
> 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: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
--------------------------
Grant Ingersoll
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: Back Compatibility of Contrib. was Re: [jira] Commented: (LUCENE-1142)
Updated Snowball package
Posted by Karl Wettin <ka...@gmail.com>.
Chris Hostetter skrev:
> ...personally i think the analysis contrib should have the same compat
> reqruitements as the core given how heavily used it is.
In this specific case it is possible to introduce the new stemmers via
one method and leave the old stemmers accessable using old methods.
But that is not a very pretty solution either. Almost the same thing as
creating a new module called snowball2.
One solution is to add a complete new i18 API with abstract support for
per language stemmer, synonyms, diacritization and what not. I have many
times thought it would be nice to have that.
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: Back Compatibility of Contrib. was Re: [jira] Commented:
(LUCENE-1142) Updated Snowball package
Posted by Chris Hostetter <ho...@fucit.org>.
: Do we require the contrib to adhere to the same back compatibility rules as
: trunk? I don't know that it has been established. Thoughts? Analysis is a
: pretty tricky one, as compared to the other packages.
we discussed this a little while back and put it on the wiki...
>> "All contribs are not created equal."
>>
>> The compatibility commitments of a contrib package can vary based on
>> it's maturity and intended usage. The README.txt file for each contrib
>> should identify it's approach to compatibility. If the README.txt file
>> for a contrib package does not address it's backwards compatibility
>> commitments users should assume it does not make any compatibility
>> commitments.
...personally i think the analysis contrib should have the same compat
reqruitements as the core given how heavily used it is.
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org