This repository was archived by the owner on Sep 16, 2021. It is now read-only.

All issues

Potential race condition in lazy futures

module: lightblue

#83

· alechenninger opened

on Apr 5, 2017

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

module: lightblue

type: enhancement

#78

· alechenninger opened

on Dec 11, 2016

Use unordered bulk requests

area: performance

module: lightblue

type: enhancement

#73

· alechenninger opened

on Nov 20, 2016

Acquire and ping document event locks in parallel batch

area: performance

module: lightblue

type: enhancement

#70

· alechenninger opened

on Oct 15, 2016

Move documentEvent and eventHandlerConfig entities to own maven modules

module: lightblue

#69

· alechenninger opened

on Sep 19, 2016

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

module: lightblue

#68

· alechenninger opened

on Sep 10, 2016

Remove domain from eventHandlerConfig and just use _id

module: lightblue

#67

· alechenninger opened

on Sep 9, 2016

Automatically add necessary metadata to lightblue if not present

module: lightblue

type: enhancement

#62

· alechenninger opened

on Jul 30, 2016

Consider renaming LightblueRequester to AsyncLightblueClient; move to lightblue client library

module: lightblue

#57

· alechenninger opened

on Jul 12, 2016

Consider grabbing more notifications than needed to circumvent lock contention

area: performance

module: lightblue

type: enhancement

#54

· alechenninger opened

on Jun 13, 2016

Generalize isSuperseded and canMergeWith beyond DocumentEvents

type: enhancement

#50

· alechenninger opened

on Apr 30, 2016

Make lightblue notification/document event processing truly transactional

area: performance

module: lightblue

type: enhancement

#45

· alechenninger opened

on Apr 26, 2016