quickwit-oss / quickwit-oss/quickwit
Supporting Google PubSub as a source
@AyWa is already working on this.
Since Aug 11, 2023.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Google PubSub is a little bit different from Kinesis, Kafka, Pulsar.
First there are no way to manuallly handle partitions. The only way to control "which consumer gets what" is by having several topics.
Second, there are no real notion of offsets.
Instead, one can create and resume from snaphosts, or by publish timestamps.
Snapshots might be very difficult for us to use, as it would require an interaction between the indexer (downstream) and the source (upstream).
Using the timestamp as a checkpoint should be ok.
TLDR:
We can ack message right away, store timestamps as checkpoints, and seek to timestamp when we restart the source.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.