1 Answer
- Newest
- Most votes
- Most comments
1
Yes, queries with with inequality conditions are not recommended because they don't scale well when the amount of data in table grows. There are currently two workarounds to overcome this problem:
- Depending on your application architecture, you may consider using Streaming feature of Amazon QLDB to process transactionRegistry records once they created or updated in the table. Steaming sends journal updates to Amazon Kinesis, which can trigger AWS Lambda function to filter out the document and call API of another component or just store it somewhere else for further processing.
- Instead of an id, you may capture the timestamp of the last processed transactionRequest record. Then the batch process can trigger Export Journal feature to export Amazon QLDB journal to Amazon S3 starting from that timestamp and then process exported files.
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
Thank you. Do you have any information if such features will be added in future (near future)?