lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omri Suissa <>
Subject Re: Nested Documents support (lucene version 3.4)
Date Wed, 22 Aug 2012 06:13:00 GMT
Hi Simon,
Thanks for the help.
This is my scenario:
My search application allow users to add manual tags to each document, each
tag have a name, type and permissions.
When searching I would like to have the following options:
1) get all the document that contains specific tag (with any type) that I
have permission to view
2) get all the document that contains specific tag with specific type that
I have permission to view

For example if I have 2 documents:
Doc A with tags:
         X (type 1, permissions: everyone)
         Y (type 1, permissions: User1, User2)
         Z (type 2, permissions: User1)

Doc B with tags:
         X (type 2, permissions: everyone)
         Y (type 4, permissions: everyone)
         Z (type 2, permissions: User1)

I'll be able to find A and B when searching for all documents with tag X,
only A if X with type 1 and non of the if tag Z and i'm User2 (and so

So nested documents could really help me where each tag is a sub document
(like sql JOIN operation).

What can I do using the current capabilities?

Thank you for the help,

On Tue, Aug 21, 2012 at 8:02 PM, Simon Svensson <> wrote:

> Hi,
> I do not have an answer to your explicit question, but this mail group
> could perhaps help you with workarounds using the current functionality.
> Are you after the search functionality (field1:a and field2:b) with child
> documents? Or grouping of the results (the sql equivalent of group by)?
> Return the first 5 entries of every group (like a Google search does per
> site)?
> // Simon
> On 2012-08-21 16:00, Omri Suissa wrote:
>> Hi everyone,
>> We are currently implementing Lucene .net in our solution and we need to
>> use the Lucene Nested Documents support that was introduce in Lucene
>> version 3.4
>> If I understand correctly the current version of Lucene .net does not
>> support this feature (and other 3.4 features), there is a timeline for the
>> 3.4 porting to .net?
>> Thank you,
>> Omri

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message