You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@inlong.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/28 11:18:01 UTC

[jira] [Updated] (INLONG-51) TubeMQ should consider multi-copies to store for each message

     [ https://issues.apache.org/jira/browse/INLONG-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated INLONG-51:
---------------------------------
    Labels: pull-request-available  (was: )

> TubeMQ should consider multi-copies to store for each message
> -------------------------------------------------------------
>
>                 Key: INLONG-51
>                 URL: https://issues.apache.org/jira/browse/INLONG-51
>             Project: Apache InLong
>          Issue Type: New Feature
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> From the perspective of big data scenarios, although the most businesses can be said that a certain data loss rate can be tolerated, there are still another businesses that want to say that they can not lose data as much as possible. Can they provide data reliability guarantees for large data scenarios? How about it?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)