maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MINDEXER-3) Add "high level" abstractions to perform searches
Date Sun, 06 Sep 2015 20:45:15 GMT

     [ https://issues.apache.org/jira/browse/MINDEXER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MINDEXER-3.
---------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Add "high level" abstractions to perform searches
> -------------------------------------------------
>
>                 Key: MINDEXER-3
>                 URL: https://issues.apache.org/jira/browse/MINDEXER-3
>             Project: Maven Indexer
>          Issue Type: New Feature
>            Reporter: Cservenak, Tamas
>
> Add "high level" abstractions to perform searches.
> While NexusIndexer interface is rather "low level" (it works with Lucene Query directly),
we should have a component that adds some "high level" abstractions to Indexer.
> Typical queries would be:
> * perform "general" search -- aka "keyword" search in Nexus (G and A fields are searched).
This could be broaden up to multiple fields.
> * search for GAV with supplied values
> * search for all plugins with provided expressions
> * etc
> And callers of these methods should not worry about _how_ the Query should be constructed,
neither worry when to fallback to use the "groups" and "rootGroups" fields in Indexer for
example, these should happen transparently, "behind the curtains".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message