You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/11/12 09:39:34 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=14207815#comment-14207815 ]
ASF subversion and git services commented on LUCENE-5736:
---------------------------------------------------------
Commit 1638717 from [~teofili] in branch 'dev/trunk'
[ https://svn.apache.org/r1638717 ]
LUCENE-5736 - adding test for caching nb classifier
> 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
> Labels: gsoc2014
> Fix For: 5.0
>
> Attachments: 0803-caching.patch, 0810-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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org