关于Azure的表二级索引 [英] About Azure Table Secondary Index

问题描述

我知道辅助指数（S）还没有实现：<一href=\"http://www.mygreatwindowsazureidea.com/forums/34192-windows-azure-feature-voting/suggestions/396314-support-secondary-indexes\"相对=nofollow>它在愿望清单和刨

I know the Secondary Index(s) is not here yet: It's in wish list and "planed"

我想获得（来自可靠来源或信息）对传入的辅助索引的一些想法（S）

I like to get some ideas (or information from the reliable source) about the incoming secondary index(s)

第一个问题：我注意到MS刨次要的指标：是意思，因为我们希望在一个表中，我们可以创建许多指标

1st question: I noticed MS planed "secondary indexes": is that mean we can create as many indexes as we want on one table

第二个问题：当前指数为 PartitionKey + RowKey ，如果上面的问题是不正确的，将二级指标是 RowKey + PartitionKey 或者我们有一个很好的机会，我们可以自定义呢？

2nd question: Current index is "PartitionKey+RowKey", if above question is not true, will the secondary index be "RowKey+PartitionKey" or we have a good chance that we can customize it?

我想获得一些想法，因为我目前设计的表，因为数据不会有太大的开始，所以我想我可以等二级索引功能，而不在这一刻创建多个表。

I like to gain some ideas because I am currently design a table, since the data won't much from beginning, so I think I can wait for the secondary index feature without create multiple tables at this moment.

请分享你的想法，或者你有任何来源，谢谢。

Please share you ideas or any source you have, thanks.

推荐答案

作为Windows Azure的MVP我没有关于表服务的辅助索引的任何信息。如果我们需要在餐桌服务多个索引，但不希望使用SQL Azure的，（不只是因为定价的...），那么我想反规范化我的数据，相同数据分割成多个表，不同的行键为指标。

As a Windows Azure MVP I don't have any information about the secondary indexes in table service. If we do need more indexes in table service, but don't want use SQL Azure, (Not just because of the pricing...) then I would like to de-normalization my data, which split the same data into more than one table, with different row key as the indexes.

这篇关于关于Azure的表二级索引的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！