Support secondary Indexes
Need to be able to sort on something other than the rowkey
andybritcliffe
shared this idea
We do still intend to support secondary indexes. However, no firm timeline has been established for when that capability will be made available. Based on our most current information, secondary indexes are not going to be released as a feature in 2011.
48 comments
-
Aaron Bird
commented
Can we get an update on when this is going to be supported?
-
Dennis
commented
This was announced as coming at the PDC conference in 2009. Three years later, I'm pretty sure we'll never see it. Microsoft has recently started a beta version of Hadoop on Azure (see https://www.hadooponazure.com)
My best bet now is that Hadoop will be the preferred approach and will meet whatever needs there may have been for secondary indexes in Azure Table Storage.
Once SQL Azure came out, there didn't seem to be any steam left behind further advancements to Table Storage. Microsoft missed the boat on this one, but I think this feature request has long since become irrelevant. There just wasn't much use for Table Storage in the way it was first released and it didn't get any real upgrades from that early version.
-
Oliver Weichhold
commented
Still no news?
-
SoftwareMK: Mikael Koskinen
commented
Aye, as many have mentioned, custom indexes are a must.
-
Anonymous
commented
I have to say that I totally agree with people saying this is a MUST for azure table storage. Really, how is it possible to use this in any sensible way without custom indexing?
EPIC FAIL!
-
David Pfeffer
commented
We are currently converting everything to use RavenDB on top of blobs for exactly this reason.
-
STonstad
commented
Epic fail. While Amazon DBS has had this feature for years it appears very likely it will never come to table. Table is on a path to obsolescence.
-
chad
commented
More than one year later (actually has been several years since this was requested by many, many people). Update the status?
-
astaykov
commented
Is there any status update since Feb 2011 on this. One year later?
-
Gimmerank
commented
I like to know: primary index is PartitionKey+RowKey, will the secondary index be: RowKey+PartitionKey or we can customize it
-
manny
commented
Its 2012. Any updates on when secondary indexes would be available. Should we plan on it being available in the near future or should we implement workarounds like storing the data multiple times with different RowKeys. As ray247 mentions not needing to make big code changes would be great and we do not want to put in unnecessary optimizations if secondary indexes are going to come by soon...
-
ray247
commented
I just posted a question/suggestion to the Azure Storage forum on this secondary index feature. http://social.msdn.microsoft.com/Forums/en-US/windowsazuredata/thread/38f07a77-cbe1-4627-9c49-29b314dbfd42
Basically not needing to make big code changes for our existing app would be great when this feature comes out. So could you make it so that we could just label any existing column and make it the secondary index, this would help avoid major code changes. Thanks.
-
Kjartan
commented
This feature is a must!!! Any news?
-
Oliver Weichhold
commented
Any updates on this would be greatly appreciated!
-
Andrew Harry commented
Hope this gets some attention from MS soon
-
zmorris
commented
MakerOfThings77 has a good idea. His suggestion would be a significant step in the right direction (ANY steps in ANY direction for Table Storage would be welcome at this point. Did Ballmer gut the storage team too....?)
-
MakerOfThings77 commented
Thanks for the update Haris. At a minimum can we just get the ability to skip N rows? I can maintain an index in Blob storage, but for a large table it is just lame to have to page though with continuation tokens to get to the 100000th item in a table. Since table is built on blob storage (so I hear) can't you make a forward only "Seek N" in the meantime? I'll make a wrapper on that for a secondary index.
-
STonstad
commented
We used to be heavily committed to Azure Table. We are now starting a slow migration to load balanced SQL Azure instances. It is a disappointing reality. Compared to Amazon Simple DB, Azure Table has few compelling features and limited comittment from Microsoft. We've learned to embrace SQL Azure...
-
Frederick Thompson
commented
Wow .... this has been here for a long time ? What's going on with this ?
-
andy.scott12
commented
don't understand what has happened here at all ? this was "coming" more than 15 months ago ? there just doesn't seem to be ANY updates being provided for Azure Table Storage at all - its being completed IGNORED. The last 2 SDK's haven't provided any new functions at all and now this is "off the roadmap" ? Why bother using ATS at all if you are never going to add new functionality to it.
