ValueError: No hash key attribute for index: {index name}

[AhmedBytesBits]

Hi,

I am receiving the following error
ValueError: No hash key attribute for index: fetch_index
Although I followed instructions as in the example

Here is the model class

class ArticleModel(Model):
    """
    Article model in DeynamoDB
    """

    @classmethod
    def _conditional_operator_check(cls, conditional_operator):
        pass

    class Meta:
        table_name = app_config.articles_table
        region = app_config.REGION
        aws_access_key_id = app_config.AWS_KEY,
        aws_secret_access_key = app_config.AWS_SECRET,

    key = UnicodeAttribute(hash_key=True)
    domain = UnicodeAttribute(null=False)
    publish_date = UTCDateTimeAttribute()
    fetch_date = UnicodeAttribute(null=False)
    fetch_time = UnicodeAttribute(null=False)
    lang = UnicodeAttribute(null=False)

    fetch_index = FetchIndex()

And here is the index class

class FetchIndex(GlobalSecondaryIndex):
    """
    Fetch Index Secondary index for Articles table
    """
    class Meta:
        read_capacity_units = 2
        write_capacity_units = 1
        index_name = 'fetch_index'
        projection = AllProjection()
    fetch_date = UnicodeAttribute(hash_key=True)
    fetch_time = UnicodeAttribute(range_key=True)

Here is my query

for article in ArticleModel.fetch_index.query("2017-07-21"):
    print("Item queried from index: {0}".format(article.key))

Note: The global index has been created via web console with same names for hash and sort keys

[andremilk]

I am experiencing this as well and it's a bit erratic.. it's almost random

[jpinner-lyft]

@ahmedrshdy what version of python and pynamodb are you using?

[madalinagal]

@jpinner-lyft I'm getting the same error using python 2.7 and pynamodb 3.1.0. Tried to upgrade pynamodb to the latest but I get the same result.

[chuckoy]

@ahmedrshdy what did you name your GSI in dynamodb? ran into the same problem and it ended up being a misconfiguration issue, I simply updated my PynamoDB GSI index_name to the value below:

class TableUserIndex(GlobalSecondaryIndex):
    class Meta:
        index_name = 'TableUserIDIndex'
        ...
    ...

then use it as you normally would

[NikitaTitov]

Hello! Same for me, here is my index

class ReportDeliveryStatusGSI(GlobalSecondaryIndex):
    class Meta:
        write_capacity_units = INTERNAL_DB_INDEX_WRITE_CAPACITY_UNITS
        read_capacity_units = INTERNAL_DB_INDEX_READ_CAPACITY_UNITS
        projection = AllProjection()
    delivery_status = NumberAttribute(hash_key=True, default=ReportStatus.CHANGED)

Model class

class Report(Model):
    class Meta:
        aws_access_key_id = INTERNAL_DB_AWS_ACCESS_KEY_ID
        aws_secret_access_key = INTERNAL_DB_AWS_SECRET_ACCESS_KEY
        table_name = DynamodbTableNames.REPORT_VERSIONS
        region = INTERNAL_DB_REGION_NAME
        host = INTERNAL_DB_ENDPOINT_URL
        write_capacity_units = INTERNAL_DB_TABLE_WRITE_CAPACITY_UNITS
        read_capacity_units = INTERNAL_DB_TABLE_READ_CAPACITY_UNITS
    delivery_status_index = ReportDeliveryStatusGSI()
    delivery_status = NumberAttribute(default=ReportStatus.CHANGED)
    idrac = NumberAttribute(hash_key=True)
    version = NumberAttribute()
    content_type = UnicodeAttribute()
    content = JSONAttribute()

And my query for example
Report.delivery_status_index.query(ReportStatus.CHANGED)

And I got the same error No hash key attribute for index

Any help please)))

[ikonst]

@NikitaTitov could you please run aws dynamodb describe-table --table-name <your-table> or provide equivalent info from the AWS console?

[emise]

I also ran into this issue, and it seems to be intermittent - after retrying the call several times it went through.

[ikonst]

I think the issue here is that the index itself is missing but the error is misleading -- should be addressed by #641. This is to be expected since, for an existing table, the GSI can take time to backfill.