esbtools event-handler issues

esbtools / event-handler

Notification in, document out.

GNU General Public License v3.0

3 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Consider using NotificationFactory and DocumentEventFactory a bit differently

#43 alechenninger opened 8 years ago
1
Consider lightblue request subtype which can have a lock association

#42 alechenninger opened 8 years ago
0
When fail to parse notifications or document events, mark them as failed

#41 alechenninger closed 8 years ago
0
Setup integration with external build/deploy tools

#40 derek63 closed 8 years ago
0
Add asynchronous 'finally' equivalent to TransformableFuture

#39 alechenninger closed 8 years ago
0
Cleanup old notifications and document events

#38 alechenninger closed 8 years ago
0
Support manually reprocessing document event; test concurrent update

#37 alechenninger closed 8 years ago
0
When batch operations fail, return result with what among batch failed (whether return or exception)

#36 alechenninger opened 8 years ago
0
Add sourceNotificationId to DocumentEventEntity

#35 alechenninger closed 8 years ago
1
Reorganize retry logic in RetryingBatchFailedMessageRoute

#34 kahowell opened 8 years ago
0
PollingDocumentEventProcessorRoute sends to document endpoint one document at a time; could use batch

#33 alechenninger opened 8 years ago
0
Add route for retrying failed messages before sending to DLQ

#32 alechenninger closed 8 years ago
4
Overloaded 'Message' term

#31 alechenninger opened 8 years ago
0
Generate metadata on build

#30 alechenninger closed 8 years ago
1
Capture current stack when request added to bulk requester

#29 alechenninger opened 8 years ago
0
Add Requester API which accepts Collection

#28 alechenninger closed 8 years ago
2
Allow getting response by index from requester

#27 alechenninger closed 8 years ago
5
Add some immediate transformable futures

#26 alechenninger closed 8 years ago
2
Also check if new event supersedes existing event (fixes #24)

#25 alechenninger closed 8 years ago
2
Need to account for superseded check not being commutative

#24 alechenninger closed 8 years ago
0
Explore explicitly modelling processing domain around batching

#23 alechenninger opened 8 years ago
0
Update bulk requester to support optimized request chaining

#22 alechenninger closed 8 years ago
19
AsyncMessageProcessorRoute

#21 alechenninger closed 8 years ago
2
Rollback instead of fail notifications if document event additions fail

#20 alechenninger closed 8 years ago
2
Update document event status post publish

#19 alechenninger closed 8 years ago
0
Add API to roll back event or notification processing transaction

#18 alechenninger opened 8 years ago
0
For lightblue impl document events, store processingDate or expirationDate?

#17 alechenninger opened 8 years ago
1
Organize packages

#16 alechenninger closed 8 years ago
2
Consider using save with upsert instead of insert + update if possible

#15 alechenninger closed 8 years ago
1
Consider other types of Notifications

#14 alechenninger closed 8 years ago
2
Pseudo-randomize order of locks acquried for document events

#13 alechenninger opened 8 years ago
0
Consider fetching another batch of documents events after we've acquired locks for document identities

#12 alechenninger opened 8 years ago
0
Some bulk updates could use request per status instead of request per entity

#11 alechenninger opened 8 years ago
1
Consider implementing distributed synchronization using ZooKeeper

#10 alechenninger opened 8 years ago
1
Lightblue repositories' dynamic config

#9 alechenninger closed 8 years ago
2
Add TTL to all lightblue locks by way of LockStrategy

#8 alechenninger closed 8 years ago
6
Update lightblue client for proper error handling in bulk requests

#7 alechenninger closed 8 years ago
0
Consider pulling up event optimization logic from lightblue impl to general routes

#6 alechenninger opened 8 years ago
1
Test BulkLightblueRequester

#5 alechenninger closed 8 years ago
0
Implement notification and event processing routes

#4 alechenninger closed 8 years ago
2
Implement LightblueNotificationRepository

#3 alechenninger closed 8 years ago
1
Implement Lightblue document event repository

#2 alechenninger closed 8 years ago
2
Consolidate lookups and bulk operations

#1 alechenninger closed 8 years ago
5