azure-table-storage

问题 I am trying to query against timestamp column on a azure table storage. I have a where condition which checks if input value is greater than timestamp value. azure Timestamp column is not a partition key or row key. I came to know querying against column which is not partition or row key will decrease performance of the query execution. My application is very slow when there are more and more records. I tried to move time stamps data to partition key data but partition key is not accepting

问题 Azure Table Storage does not support many property types (List<>, TimeSpan, etc). There are solutions like Lucifure Stash and Lokad.Cloud, but they are not compiling for DNX Core 5.0. Is there a way to add support for custom property types in Azure Tables with DNX Core? 回答1: One solution is to use reflection to iterate through all the “custom” properties of the entity and serialize them to JSON strings. We can override TableEntity’s ReadEntity and WriteEntity methods to hook de-/serialization

问题 In Windows Azure Storage, we used to do this to create a table : var tableClient = account.CreateCloudTableClient(); tableClient.CreateTableIfNotExist(TableName); I just downloaded the last version of the azure storage library (v2), and my previous code doesn't work anymore : 'Microsoft.WindowsAzure.Storage.Table.CloudTableClient' does not contain a definition for 'CreateTableIfNotExist' and no extension method 'CreateTableIfNotExist' accepting a first argument of type 'Microsoft.WindowsAzure

问题 I am running 10k tasks which each send a batch of data to an Azure Storage Table. If I use the first method below with async await that returns running tasks the tasks execute really slow and increasingly slower from a couple of seconds climbing up to 10, 100 seconds etc. If I use the second method below that returns new running tasks they run really quickly! Just a very few tens of ms per task. Why is there such a huge difference here? What am I missing? At the end of my task creation I do a

问题 I am trying to enable Linux Diagnostics for individual disks attached to the VM. I am referring to this link (https://docs.microsoft.com/en-us/azure/virtual-machines/linux/diagnostic-extension) I am using this CLI azure vm extension set vmturbo DiagnosticTest LinuxDiagnostic Microsoft.Azure.Diagnostics '3.0' --private-config-path PrivateConfig.json --public-config-path PublicConfig.json -v And this is how PrivateConfig.json looks like { "storageAccountName" : “XXXXXXXXXX”,

问题 I'm having this issue that I've been going crazy over for a few hours now. I've got a table stored in Azure that holds tasks a user wants to accomplish. Each task has a status which can be an integer value of either 1, 2 or 3 corresponding to to do, in progress or completed respectively. I'm trying to create three separate gauges which tell the user how many tasks they have in each of those three categories, but everything I've tried throws a MobileServiceInvalidOperation error and I can't

问题 I have some tables in my Azure Table Storage and need to deploy a script to populate a new column with empty data for all of them. I know that some management could be done via PowerShell, but I was unable to find any relevant example or documentation on how to perform this task. Any help would be appreciated. 回答1: Regarding the PowerShell script, please refer to the following code: Install-Module -Name AzTable $groupName="" $StorageAccountName = "" $StorageAccountKey = "" $vaule=" " $context

问题 I am trying to insert multiple rows into the Azure table service. As far as this article goes, I have understood the partition key to be able to store duplicates. However, while following this article, when I try to insert a duplicate partition key I get an error: The remote server returned an error: (409) Conflict. What could be wrong in my code? I am following it as per the second article; Or is my understanding incorrect? Also, the first article says that the row key is supposed to act as

问题 I'm considering using Fat Entities from Lokad.Cloud in a new Azure based application. At the moment I'm still trying to decide if I should go with Table Storage or SQL - I know SQL better, but TS has the potential to perform better if designed correctly. When I was reading the wiki from Lokad.Cloud I came across this page on AutoScaling. Under Limitations it says Lokad.Cloud only supports a single VM size for now: VM referred small in Windows Azure. Does this mean that I won't see any benefit

问题 The Azure Storage client was recently updated to version 2.0, and I haven't found any API that returns Task. How can I use TPL with Table Storage? .. Blob or Queue? For your reference the new API has an example here for Table Storage. 回答1: Looking through some of the source under https://github.com/WindowsAzure/azure-sdk-for-net/ it appears that they haven't had a chance to add the Task versions yet (seems odd since it specifically mentions targeting .NET 4), but the operations appear to have