You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Robert Muir (Jira)" <ji...@apache.org> on 2021/11/19 14:47:00 UTC
[jira] [Resolved] (LUCENE-10239) upgrade jflex (1.7.0 -> 1.8.2)
[ https://issues.apache.org/jira/browse/LUCENE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved LUCENE-10239.
----------------------------------
Resolution: Fixed
I've opened LUCENE-10243 to bump the unicode versions of the grammars. Will split out an issue to use the new features to simplify grammars and gradle build as well.
> upgrade jflex (1.7.0 -> 1.8.2)
> ------------------------------
>
> Key: LUCENE-10239
> URL: https://issues.apache.org/jira/browse/LUCENE-10239
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
> Fix For: 9.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> When reviewing LUCENE-10238, I noticed we still had unicode 9.0 data specified for our jflex tokenizers.
> According to the changelog I see some key benefits from upgrading to jflex 1.8.2:
> * unicode 9 -> unicode 12.1
> * remove our custom emoji regeneration via ICU, as jflex supports emoji properties directly now.
> * Less RAM at runtime to users (two stage tables): https://github.com/jflex-de/jflex/pull/697
> https://www.jflex.de/changelog.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org