[SAMZA-651] Implement message store for window operator

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: sql
• Assignee: Unassigned
• Reporter: Yi Pan
• Created: 15/Apr/15 23:39
• Updated: 15/Apr/15 23:39

Description

In window operator design (SAMZA-552), a Message Store may be needed to store all messages in the windows in retention. The Message Store should be a Key-Value store that do not need changelog. The value in the message store is always the input message, while the key of the message store could vary quite a lot based on time/tuple windows and the access pattern of messages in the window operator (e.g. different join conditions results in different access pattern to windowed messages as illustrated in SAMZA-552).

The goal of this task is to implement the following two options initially, which are considered to be common use cases:

1. Timestamp + offset as the message key
2. Some ID field + timestamp + offset as the message key