Sort Order By not respected
ShawnMac opened this issue · 4 comments
SdbNavigator doesn't seem to consistently display the returned rows as specified by "order by" clause.
select * from MotoFuze.Signals.Summary
where vdpCount > '4' order by vdpCount desc limit 25
Given the query above, SdbNavigator displays the following rows.
But the order of the rows as returned by AWS is different (and sorted corrected). Notice that the Item with itemName() = b2f30b86-3521... appears as the 2nd item as returned by AWS but is displayed as the 13th item by SdbNavigator. Is there some sort of post request sorting happening by SdbNavigator?
Thanks for the report. I've looked into this, but can not easily reproduce this issue.
- Do you see any errors reported when in the development console in chrome? (F12)
- Could you e-mail me a part of your data set so i can try and reproduce your issue with the query you used?
Thanks for the follow-up Tim and sorry for the delay of my response. I was
out of town this weekend. I'll extract my data today and send it your way.
I did check the Chrome development console while Connecting to SDB and
executing the queries.. I didn't see any error messages displayed.
Thanks,
Shawn
On Fri, Oct 3, 2014 at 4:24 PM, Tim de Koning notifications@github.com
wrote:
Thanks for the report. I've looked into this, but can not easily reproduce
this issue.
- Do you see any errors reported when in the development console in
chrome? (F12)- Could you e-mail me a part of your data set so i can try and
reproduce your issue?—
Reply to this email directly or view it on GitHub
#16 (comment).
I've uploaded sample data here: http://pastebin.com/aM9yWJQP (as JSON)
Here is the query to illustrate the issue: select * from ShawnTest
where lastProcessedDatetime > '635482196466891151' order by lastProcessedDatetime DESC
Here are the displayed results from SdbNavigator:
And here is the same query from the AWS Explorer in Visual Studio (this result matches the raw result I'm seeing returning from AWS via the Fiddler tool)
I've uploaded this data into a few SDB domains to ensure it wasn't something with the domain itself. I haven't tested with different AWS accounts but can do so if you still can't replicate my results. It seems that it's always the 2nd result that is off.
Let me know if I can provide any additional information.
Thanks,
Shawn
Hi Shawn,
Thanks for the additional info. I was able to reproduce the issue and i think i found what was causing this. I've just pushed the fix the Chrome store, so you should be able to update the plugin in your browser and it should work fine.
Please let me know if you encounter any more issues.
Regards,
Tim