Closed Bobspadger closed 6 years ago
That's reasonable, what i thought:
We may use that aws message key for testing or if we screw something up at the point we call from the queue. In the jupyter notebook i would not like to have this aws message key since it's dead.
This is not wrong. This is more a concept of a helper column or should be a groupby, it's also not unique. Actually this is only one view or groupby of many. Sure it's a conceptual important one. But it's also one we never use alone in the end. I did not fully understand how many useful views we can generate. Will hopefully come up with a jupyter notebook.
For now i don't see an usecase, maybe later. We should talk a lot about meaningful groupbys and table views.
In the jupyter notebook at 17 you have
Amazon provide both a message ID (from the SQS queue) but also a unqiue id for each update:
It may be easiest, and more reliable to use this for your index, rather than generating a new one from the asin and time changed etc?