Redshift output was tested/running on Feb 6 against a basic message/table schema. The speed was reasonable from my home machine when bulk loading (10K inserts/sec) and should be much better from machines within AWS. Synchronous individual inserts were painfully slow, about 10 per second.
Katie: ETA on the real schema?

So what do we actually need here?
- Something to read the de-orphaned results out of HDFS and put them in Redshift instead?
- Perform the de-orphaning in the pipeline data stream and populate Redshift avoiding HDFS?
- ??
The generic Redshift output is done so I am closing this. Please open a bug(s) for the implementation of the specific FHR use cases.