Support secondary Indexes
Need to be able to sort on something other than the rowkey
Restricting us to only the row key is very limiting. We currently have to maintain our own secondary indexes for other columns and this is very cumbersome, it should be a feature of the platform.
Thank you for the feedback on this feature, and we apologize for the lack of updates. We have not gotten to this feature due to the focus on delivering Disaster Recovery features such as Read-Access Geo-Redundant Storage, IaaS Disks (Page Blobs), along with other features. Our intent is to provide this feature at some point, but we do not have a timeline for when it will be delivered.
We absolutely need this! Due to the high cost and throughput limitations of DocumentDB it is not a viable alternative to having secondary indexes in table storage.
Let me give you an example of why this is critical. I have about 30 GB of event logs. I want to store these in ATS. The problem is that I need to be able to query them along multiple different axes - the company they belong to, the individual user they belong to, the date/time they came in, the event name, and so forth. And eventually, probably lots more. My current solution is to store the data "n" times, each one with a different partition-key/row-key schema, to enable querying along that particular dimension. So far so good - it's not a problem to write the data "n" times, given how well ATS performs, and how cheap it is.
But the problem is maintenance. Right now, with about 30 GB of data, if I come up with a new dimension that I need to support, it takes me at least a day to write the scripts to export and then re-import the data to the new format (because it all has to be parallelized, and needs to track state for each portion I'm running in parallel, or it would take weeks); and even if I don't ***** up on the (very complex) import/export scripts somehow, it then takes at least 1-2 days to actually get all the data over to the new table.
And that's simply not a scalable model. What happens when I don't have 30 GB of data I need to pivot, but 300 GB? Or 30 TB? The pivot scripts will take weeks to run, and maintaining any shred of consistency through the process gets very, very complicated.
I get that this is a complex problem to solve. But it doesn't make it any less complicated by telling every ATS user to come up with their own (almost certainly unoptimal and buggy) solution.
With the DocumentDB and Search services now in play, does Azure still plan to add secondary index support to Table Storage?
Yet another 6 months passed since we last heard from you MS
You can manage this by hand, I do it today and built some reusable code to maintain this. However, changing or adding indexes in the future is a pain, and with the lack of cross table transactions, I have had instances where an index did not get created. Which means if you want/need true integrity, you need to have other process/patterns in place.
So while, yeah you can do this today, other systems, even Amazon's does this now for you. I would love to not have to deal with this.
I wonder the same thing...at first glance this feature seems like an essential key ingredient, but on further examination the 'feature' can be implemented as part of the table design.
Am I right in saying that the only real benefit this feature would bring would be automatic guarantees of integrity across multiple entries? So the programmer would not need to rely on azure queues for example?
I would agree that this should be a high priority feature...but largely for non-technical reasons. Am I correct in understanding that the real problem here is a development community entrenched in the relational mindset, and who need features like this to drive adoption and improve the reputation of the platform?
John Leidegren commented
Does this even make sense? I thought the point was that you'd build out any secondary indexes much in the sense that you have to think of it as a asynchronous process that eventually indexes all your data. What else could you possibly be doing at this scale?
What Anders Madsen wrote in his comment makes a lot of sense to me.
Anders Madsen commented
Price kept in mind, I think that ATS functions and performs very well, and there's no reason why you can't index the data yourself.
I've used a radical approach, where I create Btree indexes, saved in blobs. I then use cheap small workerroles that executes SQL-like queries, and it performs very well.
Only thing to keep in mind, is that this approach creates stale indexes, so it primarily targets applications that access the table storage in an asynchronous way, e.g. reading and writing at different times of the day.
Shaun Tonstad commented
@Jeff Windows Azure Storage / Tables is something of a joke among savy cloud developers. Four years have past since this original request was made. There is no sense of urgency from MS to make this service competitive with other solutions (i.e. AWS SimpleDb). It's clear that MS lacks the expertise to improve it or the political desire given dominance of SQL Azure.
Ben Adams commented
Index Table Pattern http://msdn.microsoft.com/en-us/library/dn589791.aspx
At this point, ATS is so behind the ball compared to all the other no-sql alternatives out there that it almost seems like a waste to continue with it. Wouldn't it make better sense just to make something like RavenDB or MongoDB a first-class citizen and move forward with that?
@John Wyler, I've used Azure Tables for years now and it performs great if what you need is a key, value or key,attribute store. Yes, it will be great to have secondary index, but Azure Tables is significantly cheaper than DynamoDB, even more so that they just announced that you get 1,000,000 transactions for $0.05, and that is any size of transaction (up to 1MB entity). I can afford Azure Tables, but I can't afford DynamoDB for my business.
John Wyler commented
There is no way I'm using ATS without its support for global and local secondary indices. It appears neither SQL Azure nor Table Storage is suitable for big data applications. DynamoDB it is!
"Announced at PDC that it’s coming." - 4 years ago!
Is there any update on this? AWS is eating your lunch when it comes to table storage and honestly, we are considering moving everything to AWS just to get secondary indexes in DynamoDB. It's that big of a deal.
What is the table storage team doing? Table storage is literally the same as it was when v1 of Azure shipped 5+ years ago.
I would love to know when this is happening so we can plan accordingly. Scalable storage is a key piece of our architecture and it seems that Microsoft has abandoned it.
Tom Sawyer commented
On 2009, Dec 7, Mike Wickstrand (MS) said
"Announced at PDC that it’s coming"
Today is Oct 26, 2013. I really really really want to use Table Storage, but without secondary indexes and some LINQ support for aggregate operations it is not worth it.
Ted van der Veen commented
Or maybe implement tags that can be attached to items in the Table Storage? A bit like how tags are implemented in items in Windows Azure Caching?
My goodness, Microsoft. What are you guys thinking? This has been supposedly "in the works" for years now, and it still isn't here?
We currently have two supported options to choose from: (1) Table storage, which is basically just a glorified text file; and (2) Azure SQL, which is great, but scales like wet cement. We really need something somewhere in-between. Given any thought to supporting, say, MongoDB or CouchDB or Riak or... ? Those are currently *much* more full-featured than Azure table storage, and I can't for the life of me figure out why Azure wouldn't at least pick one to make a first-class citizen.
Rob Potter commented
Building up an index table could be implemented in application code, but I imagine that most developers have written this into their application, maintaining the indexes with every insert/delete operation. It is such a common scenario that I think it should be part of the storage platform.
I see AWS DynamoDB now supports it...
Can we get an update on when this is going to be supported?