Open nathankoerschner opened 2 years ago
Determined that the best way of doing this is to group threads under channels. Since channels have the type
attribute, it will be easy to parse the channels table for all threads.
Likewise, thread histories (thread delete and thread update events) will be sent to the channel histories table.
Included thread related events in the bot, now all of the requisite data to query thread info is sent to s3.
Since the underlying datamodel didn't change, there's no need to make any changes to this repo (discord-etl)
@clemp This issue is ready for review.
Discord threads seem to be important to distinguish. Currently, our bot parses them and stores them as channels.
In order to make thread data easy to query, they should be included in our datamodel.
To stay consistent with the rest of the model, these will have an entity table and a history table.