OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [regrep] Re: [Meeting Minutes] RS Spec review special meeting1/25/2005


Farrukh Najmi wrote:
> Farrukh Najmi wrote:
> 
>> Diego Ballve wrote:
>>
>>> Farrukh Najmi wrote:
>>> ...
>>>
>>>> * Diego: 9.2.2.2. Iterative federated query behavior not clear
>>>>  o Resolution: Agreed that intended behavior works fine. Diego
>>>>    to suggest revised text for Iterative federated query behavior
>>>
>>>
>>>
>>> ...
>>>
>>>
>>> Changes are limited to the last paragraph:
>>>
>>> Current:
>>>
>>> "When a client submits a federated iterative query, the registry MUST 
>>> use the startIndex attribute value of the original request as the 
>>> startIndex attribute value of the routed request sent to each 
>>> federation member. In such cases the registry MUST return a 
>>> totalResultCount attribute value on the federated query response to 
>>> be equal to the maximum totalResultCount attribute value returned by 
>>> a routed query response from each federation member."
>>>
>>> Suggested:
>>>
>>> "When a client submits a federated iterative query, the registry MUST 
>>> use the startIndex attribute value of the original request as the 
>>> startIndex attribute value of the routed request sent to each 
>>> federation member. The response to the original request MUST be the 
>>> union  of the results from each routed query. In such cases the 
>>> registry MUST return a totalResultCount attribute value on the 
>>> federated query response to be equal to the sum of totalResultCount 
>>> attribute values returned by each federation member."
>>>
>>> Regards,
>>> Diego
>>>
>> +1. Fixed for draft 02. Thanks Diego!
>>
> Oops I sent my +1 too soon before careful reading...
> 
> In the single registry iterative query case, the totalResultCount on an 
> AdhocQueryResponse is not the total # of results returned but the number 
> of results matched within the registry.
> 
> For this reason in the federated iterative query case the 
> totalResultCount MUST be the MAX not SUM of all individual 
> totalResultCounts.
> 
> I would rephrase your paragraph to:
> 
> "When a client submits a federated iterative query, the registry MUST 
> use the startIndex attribute value of the original request as the 
> startIndex attribute value of the routed request sent to each federation 
> member. The response to the original request MUST be the union  of the 
> results from each routed query. In such cases the registry MUST return a 
> totalResultCount attribute value on the federated query response to be 
> equal to the maximum of totalResultCount attribute values returned by 
> each federation member."
> 
> 

Then I missed the point. You are saying that, for example:
We query Reg A, federated with Reg B and Reg C.
- Query matches 4 objects in Reg A
- Query matches 5 objects in Reg B
- Query matches 3 objects in Reg C, 2 of wich are replicas from A.

totalResultCount = ?
I though MAX would return "5" in this case.
Plain SUM would be "12", but that is incorrect too.
Best answer would be "10"

Diego
-- 
Diego Ballve
Digital Artefacts Europe
http://www.digital-artefacts.fi



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]