Issues

• Potential race condition in lazy futures

  module: lightbluetype: bug
  esbtools/event-handler#83 · Filter by author alechenninger opened on Apr 5, 2017
  4

• Use array of strings "values" instead of single string "value" for documentEvent parameters

  module: lightbluetype: enhancement
  esbtools/event-handler#78 · Filter by author alechenninger opened on Dec 11, 2016

• Use unordered bulk requests

  area: performancemodule: lightbluetype: enhancement
  esbtools/event-handler#73 · Filter by author alechenninger opened on Nov 20, 2016

• Acquire and ping document event locks in parallel batch

  area: performancemodule: lightbluetype: enhancement
  esbtools/event-handler#70 · Filter by author alechenninger opened on Oct 15, 2016
  2

• Move documentEvent and eventHandlerConfig entities to own maven modules

  module: lightbluetype: refactor
  esbtools/event-handler#69 · Filter by author alechenninger opened on Sep 19, 2016
  4

• Lazy future transforms are not called if the future is already completed

  module: lightbluetype: bug
  esbtools/event-handler#68 · Filter by author alechenninger opened on Sep 10, 2016
  2

• Remove domain from eventHandlerConfig and just use _id

  module: lightbluetype: refactor
  esbtools/event-handler#67 · Filter by author alechenninger opened on Sep 9, 2016

• Automatically add necessary metadata to lightblue if not present

  module: lightbluetype: enhancement
  esbtools/event-handler#62 · Filter by author alechenninger opened on Jul 30, 2016
  1

• Consider renaming LightblueRequester to AsyncLightblueClient; move to lightblue client library

  module: lightbluetype: refactor
  esbtools/event-handler#57 · Filter by author alechenninger opened on Jul 12, 2016
  2

• Consider grabbing more notifications than needed to circumvent lock contention

  area: performancemodule: lightbluetype: enhancementtype: question
  esbtools/event-handler#54 · Filter by author alechenninger opened on Jun 13, 2016

• Generalize isSuperseded and canMergeWith beyond DocumentEvents

  module: libtype: enhancementtype: refactor
  esbtools/event-handler#50 · Filter by author alechenninger opened on Apr 30, 2016

• Make lightblue notification/document event processing truly transactional

  area: performancemodule: lightbluetype: enhancement
  esbtools/event-handler#45 · Filter by author alechenninger opened on Apr 26, 2016
  1

• Investigate flakey test in event-handler-lightblue

  module: lightbluetype: question
  esbtools/event-handler#44 · Filter by author alechenninger opened on Apr 25, 2016
  1

• Consider using NotificationFactory and DocumentEventFactory a bit differently

  type: refactor
  esbtools/event-handler#43 · Filter by author alechenninger opened on Apr 22, 2016
  1

• Consider lightblue request subtype which can have a lock association

  module: lightbluetype: enhancement
  esbtools/event-handler#42 · Filter by author alechenninger opened on Apr 19, 2016

• When batch operations fail, return result with what among batch failed (whether return or exception)

  type: enhancement
  esbtools/event-handler#36 · Filter by author alechenninger opened on Apr 12, 2016

• Reorganize retry logic in RetryingBatchFailedMessageRoute

  type: refactor
  esbtools/event-handler#34 · Filter by author kahowell opened on Apr 4, 2016

• PollingDocumentEventProcessorRoute sends to document endpoint one document at a time; could use batch

  area: performancetype: refactor
  esbtools/event-handler#33 · Filter by author alechenninger opened on Mar 31, 2016

• Overloaded 'Message' term

  type: refactor
  esbtools/event-handler#31 · Filter by author alechenninger opened on Mar 29, 2016

• Capture current stack when request added to bulk requester

  module: lightbluetype: enhancement
  esbtools/event-handler#29 · Filter by author alechenninger opened on Mar 16, 2016

• Explore explicitly modelling processing domain around batching

  type: refactor
  esbtools/event-handler#23 · Filter by author alechenninger opened on Feb 26, 2016

• Add API to roll back event or notification processing transaction

  type: enhancement
  esbtools/event-handler#18 · Filter by author alechenninger opened on Feb 8, 2016

• For lightblue impl document events, store processingDate or expirationDate?

  module: lightbluetype: question
  esbtools/event-handler#17 · Filter by author alechenninger opened on Feb 8, 2016
  1

• Pseudo-randomize order of locks acquried for document events

  module: lightbluetype: enhancement
  esbtools/event-handler#13 · Filter by author alechenninger opened on Feb 3, 2016

• Consider fetching another batch of documents events after we've acquired locks for document identities

  area: performancemodule: lightblue
  esbtools/event-handler#12 · Filter by author alechenninger opened on Feb 3, 2016