proton implementation using wrong stream type #279

Closed
opened 2026-03-28 04:23:02 +00:00 by mfreeman451 · 0 comments
Owner

Imported from GitHub.

Original GitHub issue: #778
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/778
Original created: 2025-05-14T18:13:42Z


We're creating MergeTree type streams, according to the timeplus team we would be better off using create stream name(..)

Notes:

for `create stream name(..)` this will be an append stream by default and it will work for both Timeplus Proton and Timeplus Enterprise. While MergeTree only works for single-node Timeplus, later on if your customers want to setup multi-node cluster with Timeplus Enterprise, such MergeTree won't work. However streams are created on the cluster work out of box

You can query the historical data with table(stream) or settings query_mode='table'  We may think of adding a param in your database connection if a certain API calls are always querying past data, not waiting for new data, so you don't have to set table(..) in every SQL
Imported from GitHub. Original GitHub issue: #778 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/778 Original created: 2025-05-14T18:13:42Z --- We're creating MergeTree type streams, according to the timeplus team we would be better off using `create stream name(..)` Notes: ``` for `create stream name(..)` this will be an append stream by default and it will work for both Timeplus Proton and Timeplus Enterprise. While MergeTree only works for single-node Timeplus, later on if your customers want to setup multi-node cluster with Timeplus Enterprise, such MergeTree won't work. However streams are created on the cluster work out of box You can query the historical data with table(stream) or settings query_mode='table' We may think of adding a param in your database connection if a certain API calls are always querying past data, not waiting for new data, so you don't have to set table(..) in every SQL ```
mfreeman451 2026-03-28 04:23:02 +00:00
  • closed this issue
  • added the
    eta 1d
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar#279
No description provided.