I believe we have come across a full-text index bug in Domino 6.5.4FP2. All these years, I have been convinced that a response doc was never in a view unless its parent was in the view. Testing this morning reconfirms that it is not, YET IT IS (depending on how you look at it). True - you cannot navigate to a document whose parent is not in the view – using to select all will not count a document whose parent is not there. BUT YOU WILL BE ABLE TO SEE THE DOCUMENT IF YOU DO A FULL-TEXT SEARCH FOR IT IN THE CLIENT. The document WILL be shown including values for all columns even though its parent doc is not in the view. Anyone else seen this behavior? Agree that it is a bug?
Subject: responses that are / are not in a view with hierarchy – FTI bug
Interesting… I would think that this is unintended behavior, so it should be classified as a bug. I can imagine the backend search algorithm, though, so it might be a bear to fix. Does the problem not exist prior to 6.5.4FP2?
Subject: RE: responses that are / are not in a view with hierarchy – FTI bug
I can’t answer that question. I do know that it happens with that version on my client and server. I have never seen it happen before, but I wasn’t trying to find it before.
Subject: responses that are / are not in a view with hierarchy – FTI bug
Those response docs are definitely in the view if you use SELECT Form = “Main” | @IsResponseDoc
or something like that in your selection formula. The reason you don’t see them is simply that if your view is hierarchical and their parent docs aren’t in the view then there is no place to hang their hat, so to speak.
Once you do a ft search, I guess you’re breaking the hierarchical nature of the view, and therefore they can be seen. I think this is an intended feature of ft searching, as otherwise you might get a hit on a response but not its parent, and then the response couldn’t be seen by you. So it’d say 43 hits but you’d only be able to see 42, for example.
So my feeling is that this is quirky behavior based on the difficult requirement of making a hierarchical view behave non-hierarchically for ft searches.
regards,
raphael
Subject: RE: responses that are / are not in a view with hierarchy – FTI bug
Thanks for the perspective. Still, I can’t see that it is intended to work that way.
p.s. The simple example I used did not use @IsResponseDoc or @AllDescendants, etc. It was simply myfield=“xxx”. That included the child but excluded the parent.