View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001903 | 10000-013: Aggregates | public | 2012-02-29 20:37 | 2012-08-07 18:35 | |
Reporter | Mark Rice | Assigned To | Rod Stein | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.02 | ||||
Summary | 0001903: What timestamp is returned when server timestamp requested | ||||
Description | I cannot find in the spec what to do when a server timestamp is requested for an aggregate. This does not make sense for historical aggregate requests because the source timestamp of the data is used to calculate the intervals. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
|
From Section 5.4.3 I take this to mean that you can ask for a timestamp from the server timestamp and if it is supported by the server then the server timestamp will be the one used in the aggregate calculations etc. |
|
I cannot figure out how it makes any sense to return server timestamps for aggregate data. The data is collected and aggregated based on the source timestamp. For most of the aggregates, the timestamp is specified as the beginning of the interval which is based on the source timestamp. What could "server timestamp" possibly mean in this context? I think we need to have a phone discussion on this. |
|
I re-read part 4.3 in part 11. I was misreading it when it says the request is always in source timestamps but the reply could be in any of the timestamps available. So the issue is for requests only. So yes, I agree then that there is no case for the request to come in as server timestamp because that isn’t allowed. In this case I propose that the request is rejected with Bad_TimestampsToReturnInvalid. |
|
Agreed to proposed solution in telecon. |
|
Section 5.4.3 was changed to include "If a requested timestamp is set to anyhting but the source timestamp the operation shall return the Bad_TimestampToReturnInvalid StatusCode." |
|
Making edits. |
|
fixed in 1.02.11 |
|
Agreed to close in telecon (without review). |
Date Modified | Username | Field | Change |
---|---|---|---|
2012-02-29 20:37 | Mark Rice | New Issue | |
2012-03-02 18:08 | Paul Hunkar | Status | new => assigned |
2012-03-02 18:08 | Paul Hunkar | Assigned To | => Rod Stein |
2012-04-10 02:08 | Rod Stein | Status | assigned => resolved |
2012-04-10 02:08 | Rod Stein | Resolution | open => no change required |
2012-04-10 02:08 | Rod Stein | Note Added: 0003479 | |
2012-04-10 12:33 | Mark Rice | Status | resolved => feedback |
2012-04-10 12:33 | Mark Rice | Resolution | no change required => reopened |
2012-04-10 12:33 | Mark Rice | Note Added: 0003495 | |
2012-04-10 20:14 | Rod Stein | Note Added: 0003502 | |
2012-04-17 16:33 | Jim Luth | Status | feedback => assigned |
2012-04-17 16:33 | Jim Luth | Note Added: 0003589 | |
2012-07-25 04:28 | Rod Stein | Status | assigned => resolved |
2012-07-25 04:28 | Rod Stein | Resolution | reopened => fixed |
2012-07-25 04:28 | Rod Stein | Note Added: 0003918 | |
2012-07-25 04:29 | Rod Stein | Status | resolved => feedback |
2012-07-25 04:29 | Rod Stein | Resolution | fixed => reopened |
2012-07-25 04:29 | Rod Stein | Note Added: 0003919 | |
2012-07-25 04:30 | Rod Stein | Status | feedback => resolved |
2012-07-25 04:30 | Rod Stein | Resolution | reopened => fixed |
2012-07-25 04:30 | Rod Stein | Note Added: 0003920 | |
2012-08-07 18:35 | Jim Luth | Status | resolved => closed |
2012-08-07 18:35 | Jim Luth | Note Added: 0003957 | |
2012-08-07 18:35 | Jim Luth | Fixed in Version | => 1.02 |