Skip to content
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

Support for GSI for geohash queries #46

Open
mdesanti opened this issue Sep 23, 2020 · 0 comments
Open

Support for GSI for geohash queries #46

mdesanti opened this issue Sep 23, 2020 · 0 comments

Comments

@mdesanti
Copy link

I'm building an application that stores the latest position for a vehicle. The vehicle ID will always stay the same but its position will change as the vehicle moves.

With the library as is, it is quite complicated to implement. The solution I figured out was using a GSI to store the vehicle ID, querying the record to get the partition key and then update the record. However, this requires a new element to be created since the partition key and range key will be different (different position, hence different partition and sort key) and deleting the old record.

It would be a great feature if the user can decide whether to use the library as is or to store the location information in a GSI. In my case it would mean that I query over the GSI and manage updates through the partition key and range key that I decide to use.

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

No branches or pull requests

1 participant