Hey Daniel, Pardon if you've already done this and it's insufficient...
For the sub-tree problem it's also reasonable to create a multiple fields in the doc for each "prefix" of the path. So "/fred/lives/in/flintstone" would generate fields with values (either un_analyzed or with the KeywordAnalyzer) /fred/lives/in/flintstone /fred/lives/in /fred/lives /fred / Then a simple query ( path:"/fred" ) would return all documents with a path beginning with "/fred". Alternatively, prefix queries or a custom analyzer would also work. As you're looking at the more sophisticated 4.8 features this is probably a little simplistic for your needs. Just thought I'd pitch in. --Andy On 18 January 2017 at 10:13, Van Den Berghe, Vincent < [email protected]> wrote: > Hello Daniel, > > This is really a question for the user part of the forum. > Have a look at https://www.myget.org/feed/lucene-net/package/nuget/ > Lucene.Net > Lucene.NET 4.8 contains what you need, and works reasonably well. > > Vincent > > From: Daniel Beer [mailto:[email protected]] > Sent: Wednesday, January 18, 2017 10:29 AM > To: [email protected] > Subject: Lucene.Net 4.X release > > Dear Lucene developers, > > we use Lucene.Net in our products written with C#. Now we need a kind of > search in trees and deliver the matched subtree. With newer Lucene version > we could do that (taxonomys, faccets, nested docs, joins) but not with > Lucene 3.03. > > This leads to my question: Is it planned to release new Lucene.Net > versions and when? > > Thank you in advance! > > Greetings from Weimar/ Germany, > Dr.-Ing. Daniel G. Beer > Software engineer > > f:data GmbH > Bauhausstraße 7c > 99423 Weimar > > Tel: 0 36 43 - 77 81 400 > Fax: 0 36 43 - 77 81 401 > Mail: [email protected]<mailto:[email protected]> > Net: www.fdata.de<http://www.fdata.de/> > > Geschäftsführer: > Dr. habil. Klaus Schiller > Dipl.-Inf. Frank von der Weth > > Amtsgericht Jena HRB 100813 > > USt-IdNr.: DE 150109650 > St-Nr.: 162/108/03479 > > [cid:[email protected]] > >
