commit | c7236adc3cb659e65ae5ce53b7156569d7f50ebd | [log] [tgz] |
---|---|---|
author | mauricebarnum <mbarnum@splunk.com> | Wed Sep 08 15:25:33 2021 -0700 |
committer | GitHub <noreply@github.com> | Wed Sep 08 15:25:33 2021 -0700 |
tree | 2440b8b8ba7c9b0bc9608012e8c28c68678e3e5b | |
parent | 97818f5123999396e66f5246420d3c7e3d25f53d [diff] |
[STREAMSTORAGE] support an optional time to live (TTL) on a per table basis === MOTIVIATION Bookkeeper's state store is often used, especially through Pulsar functions, to store processing state in a streaming application which require persistent short term storage. By allowing clients to set a TTL, this data will get cleaned up by the system automatically. === CHANGES Specify the TTL via stream.StreamConfiguration.ttlSeconds, default is an infinite TTL. Note that changing the TTL on existing stream will have no effect until the stream is next loaded by a storage container. Update RocksDB to 6.22.1.1 to address failures when using TtlDb. Descriptions of the changes in this PR: ### Motivation (Explain: why you're making that change, what is the problem you're trying to solve) ### Changes (Describe: what changes you have made) Master Issue: #<master-issue-number> Reviewers: Henry Saputra <hsaputra@apache.org>, Enrico Olivelli <eolivelli@gmail.com>, Prashant Kumar <None> This closes #2775 from mauricebarnum/stream-table-expiration and squashes the following commits: 50471add7 [Maurice Barnum] update LICENSE files for rocksdb-6.22.1.1 caa8532d4 [Maurice Barnum] [STATESTORE] support an optional time to live (TTL) on a per table basis
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.