You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Target release
Epic
Document statusDRAFT
Document owner

Joe Witt

Designer
Developers
QA

Goals

  • Provide a nice user experience and feature set for supporting dataflows involving Avro formatted data including the ability to easily view, edit, split, combine, and route such data.

Background and strategic fit

Usage of Avro in and around Big Data projects is increasingly common.  We should build a content viewer for Avro data, which allows a user to look at the content of a given Avro message based on the schema.  We should also provide a mechanism to manipulate the content of Avro messages to insert or update values but also to perform schema evolution or transformation.  Avro data can tend to arrive in bundles so splitting them is useful to enable individual message handling/routing cases.  The reverse then is also true which is it is useful to be able to merge Avro messages based on like-schema.  Finally, being able to run queries against avro data to make routing decisions is also valuable and given the JSON-based schema design is quite doable.

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1
2    

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • No labels