Removed duplicate attribute name check for indexes

[pokermanx]

Since DynamoDB allows to have multiple indexes with duplicate column names this check is not needed.

[whimzyLive]

@pokermanx Thanks for raise this PR.

Can you provide more information on why is this required? i.e an example scenario?

Thanks

[pokermanx]

hey, sorry for delayed response.

Example: A table that has 2 indexes that share a column. One index has pk as userName and sk status, other one has pk as userEmail and sk status. Setting indexes as

UserNameIndex: {
  type: INDEX_TYPE.GSI,
  partitionKey: 'userName',
  sortKey: 'status',
},
UserEmailIndex: {
  type: INDEX_TYPE.GSI,
  partitionKey: 'userEmail',
  sortKey: 'status',
}

will throw a Failed to parse entity error

[eulerchavez]

Hi!

Is there any status for this feature?

@whimzyLive

[reestolonio]

I'm having the same issue and was forced to create new columns unique for each index.

[dremonkey]

Having the same issue. And agree that this check is unnecessary. DynamoDB supports the above index config without any issues.

[seriousjelly]

Any updates here? Having the same issue having shared columns... It's been open for a while now, any updates on when this can be merged in?