On Tue, Nov 25, 2014 at 12:22 PM, Tamas Cservenak <[email protected]> wrote:
> Hi there, > > 1) yes, indexing context retains the artefact “origin” (ie. repo), so you > need context per origin. Sadly, the 1 index per context is current > limitation of maven indexer, but this problem is known. Created > http://jira.codehaus.org/browse/MINDEXER-93 > > 2) Yes, merged context is basically delegating to member contexts. under > the hud, it uses Lucene’s MultiReader to actually perform the search. > I have solved the search problem for now by using the SearchEngine component and issuing an IteratorSearchRequest on a list of IndexingContexts to get paginated results. Will have to see how that works on the long run. Thanks, Eduard > Re ranging, there are already issues (or problem spread across multiple > issues), most notably this one > http://jira.codehaus.org/browse/MINDEXER-8 > > 3) I think yes. Currently, indexer is being transitioned from Plexus to > JSR330, and as you see in examples, it should work with any container > supporting it. re “manually wiring”, in latest releases you might be able > to do it, but in older ones probably not, as Plexus supported field > injection only, and some of those member was not exposed via getter/setter. > See > http://jira.codehaus.org/browse/MINDEXER-80 > > > -- > Thanks, > ~t~ > > On 21 Nov 2014 at 18:08:26, Eduard Moraru ([email protected]) wrote: > > Hi, > > I have recently started playing with the maven indexer [1], following the > examples [2], and I have some questions (since AFAIS, documentation is > practically unexistent on the matter): > > 1) From what I can understand, you need an IndexingContext for each > repository you plan to index. This makes you end up with n lucene indexes, > one for each repository. Is there any way that I could have just 1 lucene > index, with all my repositories indexed in the same place? If the main > purpose is searchig, why scatter the indexed information across n indexes > and make the whole process dificult? Maybe I`m missing something. > > 2) On the same line as the first question, when it comes to searching, it > seems that I can use a MergedIndexingContext to perform a search on > multiple (all) indexed repositories (IndexingContexts). How does this merge > the search results? I assume it takes each lucene index and queries it > individually, but this probably means that the lucene scores of these > merged results are completely messed up and ureliable, right? > Any suggestions on how to properly perform search over multiple indexed > repositories? > > 3) About the Plexus Container: Am I forced to initialize and use one, or > can I/should manually instantiate the default implementations and use them > instead? > > I`ll probably come up with more questions along the way, hope someone will > find the time to guide me on the right path. > > Thanks, > Eduard > > ---------- > [1] https://github.com/apache/maven-indexer/ > [2] > > https://github.com/apache/maven-indexer/tree/master/indexer-examples/indexer-examples-basic >
