theburningmonk/ReactoKinesix issues and pull requests

#65 - Call IRecordProcessorFactory.CreateNew fro every shard in every server

Issue - State: open - Opened by alejandro-osorio over 6 years ago

#64 - Update paket to address TLS deprecation

Pull Request - State: closed - Opened by forki over 6 years ago

#63 - Fixing build error on Mac OS X

Pull Request - State: closed - Opened by wallymathieu almost 7 years ago - 1 comment

#62 - DynamoDBTableSuffix can't be configured ?

Issue - State: open - Opened by popbee over 7 years ago

#61 - Ability to specify iterator type on initialization

Issue - State: closed - Opened by robertaves almost 9 years ago - 4 comments

#60 - Support for DynamoDb Streams?

Issue - State: open - Opened by caindy about 9 years ago - 1 comment
Labels: enhancement

#59 - Unable to continue processing stream if stream was recreated

Issue - State: open - Opened by theburningmonk over 9 years ago - 7 comments
Labels: bug

#58 - AWSconfigs and hiding credentials

Issue - State: closed - Opened by luck02 over 9 years ago - 2 comments

#57 - Role of ReactoKinesix vs. Kinesis Client Library

Issue - State: closed - Opened by luck02 over 9 years ago - 3 comments

#56 - Expired Iterator Exception

Issue - State: closed - Opened by juliensydney over 9 years ago - 7 comments
Labels: bug

#55 - Track record Timestamp along in checkpoint

Issue - State: closed - Opened by theburningmonk over 9 years ago - 2 comments
Labels: enhancement

#54 - Slice up received batch into smaller batches for the consumer's processor

Issue - State: closed - Opened by theburningmonk over 9 years ago

#53 - Save checkpoint even when processing batch failed

Issue - State: open - Opened by theburningmonk over 9 years ago
Labels: question

#52 - Memory leak when processing large amounts of messages

Issue - State: closed - Opened by khanage almost 10 years ago - 8 comments

#51 - Kinesis client app not logging+

Issue - State: closed - Opened by andyg75 almost 10 years ago - 24 comments

#50 - Incorporate the new PutRecords API

Issue - State: open - Opened by theburningmonk almost 10 years ago
Labels: enhancement

#49 - Problem Disposing App

Issue - State: closed - Opened by andyg75 about 10 years ago - 11 comments

#48 - Getting an exception after a while with standard configuration

Issue - State: closed - Opened by marcosavini about 10 years ago - 5 comments

#47 - Take in a processor factory instead of an instance of a processor

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#46 - Publish processing metrics to cloudwatch

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#45 - Review the default configuration values

Issue - State: open - Opened by theburningmonk almost 11 years ago

#44 - Give processor power to decide when to checkpoint in the stream

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: question

#43 - Optimization mode

Issue - State: open - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#42 - Deal with streams with large number of shards

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#41 - Add a Bitdeli Badge to README

Pull Request - State: closed - Opened by bitdeli-chef almost 11 years ago

#40 - Add C# example

Issue - State: closed - Opened by theburningmonk almost 11 years ago

#39 - Add validation for handover request expiry

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#38 - Add another type/helper for pushing to Kinesis?

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement, question

#37 - Expose some events via public interface

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#36 - App tries to issue handover request even though another request has been issued in previous cycle

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: bug

#35 - Update README

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#34 - Expose a wrapper Record type which exposes data as byte[] instead

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#33 - Forget shards that are no longer around

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#32 - Change naming so that the term worker is not ambigious

Issue - State: closed - Opened by theburningmonk almost 11 years ago

#31 - When the first record fails, get match case incomplete error

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: bug

#30 - Remember stopped workers so that it doesn't just get started by the timer

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#29 - Dispose method on the app doesn't return

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: bug

#28 - Investigate best way to orchestrate unit tests

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement, question

#27 - Use mid-level table helpers for DynamoDB instead of raw client

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement, wontfix

#26 - Add mechanism for requesting handover

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#25 - Two workers can start process the same shard

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: bug

#24 - Allow configuration to be updated at runtime

Issue - State: open - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#23 - Allow changing of processor at runtime

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#22 - Allow consumer to make decisions around what to do when a record cannot be processed

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#21 - The app could remember closed shards at startup

Issue - State: open - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#20 - Handle the case that processing of a batch is interrupted with user commands

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#19 - Better handling for closed shards

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#18 - Handle error in KinesisUtils.getRecords

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#17 - Investigate possibility of ILMerge the AWSSDK and log4net dependencies

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: question

#16 - Handle the case that another worker is processing the shard

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#15 - Validate against negative value for MaxDynamoDBRetries in config

Issue - State: closed - Opened by theburningmonk almost 11 years ago

#14 - Extract functionalities as interfaces

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#13 - Handle addition of shards

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#12 - Disposing of the application should auto dispose of all the workers

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#11 - Allow workers to retry the initialization step

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#10 - Allow retries on DynamoDB ops

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#9 - Fix project folder name

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#8 - Stop consumer from being to accidentally start two instances of ReactoKinesixApp with same name

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#7 - Rather than taking in Action, give the consumer a simple interface to implement?

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#6 - Handle removal of shards

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#5 - Allow individual workers to be stopped

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#4 - Periodically look for shards not being processed and take over

Issue - State: closed - Opened by theburningmonk almost 11 years ago - 1 comment
Labels: enhancement

#3 - Handle exceptions when getting current shard status

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#2 - Better handling of exception when trying to create dynamodb row for shard

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

#1 - Graceful handling of race condition trying to create dynamodb state table

Issue - State: closed - Opened by theburningmonk almost 11 years ago
Labels: enhancement

GitHub / theburningmonk/ReactoKinesix issues and pull requests