TrivadisPF kafka-backup issues

TrivadisPF / kafka-backup

Kafka Backup to S3

4 stars 4 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Bump aws-java-sdk-s3 from 1.11.570 to 1.12.261

#39 dependabot[bot] opened 2 years ago
0
Bump junit from 4.12 to 4.13.1 in /util/kafka-message-generator

#38 dependabot[bot] opened 3 years ago
0
Error when setting s3.compression.type

#37 gschmutz opened 5 years ago
0
Adding changes to manage the manual partition offset assignment to consumer group

#36 antonioiorfino closed 5 years ago
0
Update consumer offset after the restore

#35 antonioiorfino closed 5 years ago
0
Performance improvments

#34 antonioiorfino closed 5 years ago
0
Compacted log backup management. First version released

#33 antonioiorfino closed 5 years ago
0
Compacted log backup management. First version released

#32 antonioiorfino closed 5 years ago
0
Retention management and multi-topic restore

#31 antonioiorfino closed 5 years ago
0
Backup of Compaced Log Topics

#30 gschmutz closed 5 years ago
3
Features

#29 antonioiorfino closed 5 years ago
0
Kafka Backup/Restore Performance Test Bed

#28 gschmutz opened 5 years ago
1
Features

#27 antonioiorfino closed 5 years ago
0
Clarify how a backup is restarted, once a restore has been done

#26 gschmutz opened 5 years ago
0
Added technical custom header properties

#25 antonioiorfino closed 5 years ago
0
Issue 22

#24 antonioiorfino closed 5 years ago
0
first draft release

#23 antonioiorfino closed 5 years ago
0
Offset of produced record not available in Kafka Connect Sink Connector

#22 gschmutz closed 5 years ago
1
Handle increase/decrease number of partition on Kafka topic

#21 gschmutz opened 5 years ago
0
Investigate S3 Batch for doing batch operation on the backed-up data

#20 gschmutz closed 5 years ago
1
S3 Multipart Upload - high-level or low-level?

#19 gschmutz closed 5 years ago
1
Test back-up and restore the topic of the Schema Registry

#18 gschmutz opened 5 years ago
0
Make a test with S3 Connector of Confluent to check how much data is lost in case of Topic delete

#17 gschmutz opened 5 years ago
0
initial design

#16 chiodonia closed 5 years ago
0
Investigate what happens to committed offset if a Topic is deleted

#15 gschmutz closed 5 years ago
2
Test Kafka Consumer with an higher offset than the actual highwatermark

#14 gschmutz opened 5 years ago
0
Implement Consumer Reset upon Restore

#13 gschmutz opened 5 years ago
0
Make sure that upon restore the data is not backed-up again

#12 gschmutz opened 5 years ago
0
Make Offset of record in topic available in Writer implementations

#11 gschmutz closed 5 years ago
1
Allow backup data to be queried using SQL

#10 gschmutz opened 5 years ago
0
Implement Protobuf Writer and Reader

#9 gschmutz opened 5 years ago
0
Support different cloud providers

#8 gschmutz opened 5 years ago
0
Test that the data is still uploaded to backup, event if there is an error because of the topic being deleted

#7 gschmutz opened 5 years ago
0
Implement Backup Monitoring

#6 gschmutz opened 5 years ago
0
Data Retention on backup data

#5 gschmutz closed 5 years ago
1
Implement offset translation index to map from original offset to "recovered" offset

#4 gschmutz opened 5 years ago
1
Implement additional, technical header properties upon restore

#3 gschmutz opened 5 years ago
2
Check if S3 Select can be used to more efficiently restore from S3

#2 gschmutz opened 5 years ago
0
Implement Avro Writer and Reader

#1 gschmutz closed 5 years ago
0