Hi,

In our system, we use logical deletion (although manually, not using @SqlDelete). I found that I can easily exclude deleted entities from the search results using a Filter on the @Indexed class. However, we have a slightly different case.

Let's say we have an @Indexed Partner entity, which has associated Addresses (@IndexEmbedded), and address entities have a String location field (nb: this is not the real case, just a simple example). For some reason, I can delete Address entities only logically, that is by setting a deleted flag to true. In this scenario, I want to search for partners by entering a location, and I want to have all partners in the result list which has a location that matches what I entered. This is easily achieved by using @Index on Partner, @IndexEmbedded on Partner.addresses, and @Field on Address.location, and searching for "addresses.location" fields. But this will match deleted locations as well.

I cannot figure out how to exclude logically deleted locations from my search.

Well, the only "solution" I can see for now is to implement special bridges for the Address entity that "hides" all of its property values from lucene when the entity is marked as deleted.

Thanks in advance

you could target the Address for queries making them @Indexed too and adding a "deleted=false" clause the the query, then getting the Partner from the relation.

This happens because the flattened nature of the Lucene index.
When you use @IndexedEmbedded, all embedded fields are thrown together as part of the embedding object, as a result the information of which embedded fields 'belong together' is lost and you cannot do such queries via the embedding object.

E.g. : a partner could have the following Document entry in the index:

id
adresses.location
adresses.location
addresses.deleted < To which of the 'location' fields do the 'deleted' fields belong? No way to tell because this information isn't there.
addresses.deleted <

Another possible solution would be to cut the Partner-Address link when you do a logical deletion. The Partner will then be reindexed without the 'deleted' Address.

Sanne: that's possible in the example above, but unfortunately the real entity structure is much more complex.

Removing them from the relation sounds feasible (and useful anyway), I'll try that, thanks for your replies.

Gabor

cool, seems a clever solution.

Gabor, let us know how it goes.

Hi, sorry for the late reply, I've been busy doing some other stuff.

So, removing the deleted item from the containing collection explicitly solved the issue.

(Nb, i'm still using 3.1.1GA, so due to http://opensource.atlassian.com/project ... SEARCH-391 I reindex the root entity after the removal. I guess in 3.1.2 this kind deletion works at deeper levels as well).

Thank you for your answers!