[
https://issues.apache.org/jira/browse/LUCENE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446517#comment-17446517
]
ASF subversion and git services commented on LUCENE-10239:
----------------------------------------------------------
Commit ee56d31425772058cbe90d25915112653ce36028 in lucene's branch
refs/heads/branch_9x from Robert Muir
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=ee56d31 ]
LUCENE-10239: upgrade jflex (1.7.0 -> 1.8.2) (#452)
Upgrade jflex.
Change doesn't alter the behavior of any of the analyzers (unicode
version or grammar refactorings), just the minimal to get new tooling
working.
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
