[
https://issues.apache.org/jira/browse/SOLR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629065#action_12629065
]
Noble Paul commented on SOLR-651:
---------------------------------
The output looks fine . may be we can improve on iterations. We should add the
uniqueKey value if it exists . That is the only way we the user can correlate
it with the actual results
{code}
<lst name="doc-3">
<str name="<unique-key-field-name><unique-key-value></str>
<lst name="cat">
....
{code}
another observation is this gets a searcher and does not do a decref() after
the use. The operations must be put in
{code:java}
try{
//the operations
}finally{
searcher.decref();
}
{code}
A suggestion on the name why not make it all lowercase. tvrh instead of tvRH
Most of the users may not need the "results" so it must be able to be used
separately as a requesthandler register it as "/tvrh"
> A SearchComponent for fetching TF-IDF values
> --------------------------------------------
>
> Key: SOLR-651
> URL: https://issues.apache.org/jira/browse/SOLR-651
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 1.3
> Reporter: Noble Paul
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-651.patch
>
>
> A SearchComponent that can return TF-IDF vector for any given document in the
> SOLR index
> Query : A Document Number / a query identifying a Document
> Response : A Map of term vs.TF-IDF value of every term in the Selected
> Document
> Why ?
> Most of the Machine Learning Algorithms work on TFIDF representation of
> documents, hence adding a Request Handler proving the TFIDF representation
> will pave the way for incorporating Learning Paradigms to SOLR framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
