[ 
https://issues.apache.org/jira/browse/BLUR-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vikrant Navalgund updated BLUR-292:
-----------------------------------

    Attachment: BLUR-292-MASTER.patch

Hello Aaron,
By following the description I think I understand the gist of the issue here. 
Please review the patch and let me know if my understanding is correct. 

I have changed the implementation to do the following:
1. Set the query start time correctly in the QueryStatus ctor.
2. Set the query start time correctly in the BlurQuery object whether the query 
is via the controller or directly on the shard server. 

The returned BlurQuery object will have the correctly populated start time. For 
example, when we get a 'BlurResults' we can find the query start time by doing 
a BlurResults.getQuery().getStartTime())

Test:
Without the change (Controller/Shard Server)
<Sample query>
Total Results: 1
Query start Time: 0
BlurResult(locationId:null, score:1.1952736377716064, 
fetchResult:FetchResult(exists:true, deleted:false, table:employee, 
rowResult:FetchRowResult(row:Row(id:1, records:null, recordCount:2)), 
recordResult:null))

With the Change (Controller/Shard Server)
<Sample query>
Total Results: 1
Query start Time: 1384008931601
BlurResult(locationId:null, score:1.1952736377716064, 
fetchResult:FetchResult(exists:true, deleted:false, table:employee, 
rowResult:FetchRowResult(row:Row(id:1, records:null, recordCount:2)), 
recordResult:null))

Regards,
Vikrant

> Query Status Start Time is always 0
> -----------------------------------
>
>                 Key: BLUR-292
>                 URL: https://issues.apache.org/jira/browse/BLUR-292
>             Project: Apache Blur
>          Issue Type: Bug
>          Components: Blur
>    Affects Versions: 0.2.0, 0.3.0, 0.2.1
>            Reporter: Chris Rohr
>         Attachments: BLUR-292-MASTER.patch
>
>
> The QueryStatus object has a field for start time which I assume is for the 
> server date/time that the query was received by Blur, however, this value is 
> always 0.  It would be handy in determining load (and running time) if that 
> value was populated.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to