JONATHAN LESSINGER A CRITIQUE OF CQL

PLAN 1.Background (How CQL, STREAM work) 2.Issues

BACKGROUND (BRIEFLY)

Data model Stream {,,,,,…}

BACKGROUND (BRIEFLY) Data model Relation t 0 -> {s 0 } t 1 -> {s 1, s 1 } t 2 -> {s 2, s 3 }

ISSUES

“…exploiting well-understood relational semantics (and by extension relational rewrites and execution strategies)”

ISSUES “Intuitive” query

ISSUES

PosSpeedStr Output Filter speed > 65

ISSUES “Our query plan generator is still fairly naive, using hard-coded heuristics to generate query plans.”

ISSUES

earlier timestamps N=5 ? …

CONCLUSION No stream -> stream operators Forcing mostly relation -> relation Should be optimizing stream operations, Not reusing old relational techniques Unintuitive queries, opaque syntax Aurora’s system is clearer, gives user more control Nondeterministic Tuple-based windows Not necessarily what user wants

CONCLUSION Thank you