You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2021/11/27 23:38:05 UTC
[GitHub] [lucene] mocobeta commented on pull request #482: Use the same analysis chain to StandardAnalyzer (a follow-up of #480)
mocobeta commented on pull request #482:
URL: https://github.com/apache/lucene/pull/482#issuecomment-980806417
I replaced the default to `StandardAnalyzer`.
> I did some quick tests. I was expecting to see the standard analyzer defaults already predefined in the UI.
> As this is not the case, I would stay with new StandardAnalyzer(). It is easier and useful.
Yes - while StandardAnalyzer is already used as the default (in 9.0), that is defined in the UI layer. My intention here is that set the default in the model layer; though the difference is not visible in the UI, this is more manageable and test-friendly.
> I had some other idea: You could also add a line to enter the class name of an Analyzer and add a button "Instantiate class (requires no-arg constructor)".
This is definitely possible, but some work is needed (adding a UI component requires layout rebalancing and proper event handling); can come later.
Here is the default look of the Luke Analysis UI with the patch (no difference from 9.0, in terms of the user interface).
I'll push it to the main soon.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org