Skip to content

fix(EnhancedClient): Correctly Identify Index attributes #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 17, 2023

Conversation

texastony
Copy link
Contributor

Issue #, if available:

Description of changes:
TableSchema's store Index information in indices, NOT keyAttributes.
keyAttributes includes Index information,
but also includes other information about non-Index related attributes.

For example, the Enhanced Client's AutoGeneratedTimestampRecordExtension persists
non-index information in keyAttributes.

Furthermore, the Java Doc for keyAttributes reads:

Returns metadata about all the known 'key' attributes for this table, such as primary and secondary index keys, or any other attribute that forms part of the structure of the table.

While indices reads:

Returns metadata about all the known indices for this table.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Table Schema's store Index information in `indices`,
NOT `keyAttributes`.

`keyAttributes` includes Index information,
but also includes other information.
@texastony texastony merged commit 6280ba4 into main Jul 17, 2023
@texastony texastony deleted the tony-fix-enhanced-client-index-identification branch July 17, 2023 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants