[ http://jira.codehaus.org/browse/MRM-127?page=comments#action_70571 ] Milos Kleint commented on MRM-127: ----------------------------------
one more thing that comes to mind. if we are to support the usecase where one downloads the index from a remote repository and works with it locally, then it's crucial that the searcher code works only on top of the index files and never contacts the remote repository (it used to do for poms I suppose where the pom was reparsed and returned from the SearchHit - not sure if it's still in the codebase) > refactor and review indexing and search > --------------------------------------- > > Key: MRM-127 > URL: http://jira.codehaus.org/browse/MRM-127 > Project: Maven Repository Manager > Issue Type: Bug > Components: indexing > Affects Versions: 1.0-beta-1 > Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > the indexing that is currently in place doesn't seem to be working well. > - creating the metadata index erases all artifacts > - the ms count for the initial index seems shorter than it takes > - design improvements needed > for search: > - general search simply iterates all fields looking for keywords, which > probably doesn't rank optimally > - search fails on "maven" as it tries to load a metadata file that contains > it incorrectly. It shouldn't need to read the metadata files of the search > results. > - general search doesn't appear to search metadata > - design improvements needed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
