Search

Azure Storage Emulator crash with boolean values in filter query by ants_super

Active

1
0
Sign in
to vote
Type: Bug
ID: 778521
Opened: 2/4/2013 11:22:15 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
This issue is specific to the Storage Emulator in the Windows Azure October 2012 SDK.

When performing a query that contains a standalone Boolean, the emulator will return an Internal Error. For example take the following query:

(false and (Phone eq '')) or (false and (MobilePhone eq '')) or (false and (Email eq ''))

will return the following error:

Server encountered an internal error. Please try again after some time.

Queries such as this can be the result of a complex query performed in LINQ using the Azure .NET Storage Library.

Queries like this run correctly in the production Azure Storage Service, and also in previous versions of the Storage Emulator.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. Perform a REST query on the Storage Emulator that contains a standalone boolean, e.g.: (false and (Phone eq '')) or (false and (MobilePhone eq '')) or (false and (Email eq ''))

2. An Internal Error will be returned instead of the correct response.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Server encountered an internal error. Please try again after some time.

Expected results

An XML response containing the relevant entities from the storage server.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/5/2013 at 2:18 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/4/2013 at 11:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.