You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2014/08/08 10:57:12 UTC
[jira] [Commented] (LUCENE-5736) Separate the classifiers to online
and caching where possible
[ https://issues.apache.org/jira/browse/LUCENE-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090493#comment-14090493 ]
Tommaso Teofili commented on LUCENE-5736:
-----------------------------------------
the second patch looks better, the only thing I would change is extending from _SimpleNaiveBayesClassifier_ and avoid rewriting the same methods that do not change in the caching version.
> Separate the classifiers to online and caching where possible
> -------------------------------------------------------------
>
> Key: LUCENE-5736
> URL: https://issues.apache.org/jira/browse/LUCENE-5736
> Project: Lucene - Core
> Issue Type: Sub-task
> Components: modules/classification
> Reporter: Gergő Törcsvári
> Assignee: Tommaso Teofili
> Attachments: 0803-caching.patch, CachingNaiveBayesClassifier.java
>
>
> The Lucene classifier implementations are now near onlines if they get a near realtime reader. It is good for the users whoes have a continously changing dataset, but slow for not changing datasets.
> The idea is: What if we implement a cache and speed up the results where it is possible.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org