Thanks Andrew ! That would be fantastic ! Even if your not successful at the trivial use case, just having a look at our source code and providing your comments or thoughts in our code on a forked branch as you explore and investigate...would be tremendously useful to us !
-Thad +ThadGuidry <https://www.google.com/+ThadGuidry> On Wed, Jun 14, 2017 at 1:25 PM Andrew Psaltis <psaltis.and...@gmail.com> wrote: > Thad, > Based on your description that OpenRefine uses similar techniques as > Zeeplin then I *think* the reading and writing will work. > > The Undo/Redo I am fuzzy on as. > > I will try over the next couple of days and see if I can make something > like this work (at lest a trivial use case). Personally I think it would be > cool to allow business users to wrangle data with OpenRefine with the power > of Flink behind it. > > > > On Wed, Jun 14, 2017 at 7:53 PM, Thad Guidry <thadgui...@gmail.com> wrote: > > > Andrew, > > > > So you idea is that Flink could be used as a storage abstraction layer > for > > OpenRefine ? Where OpenRefine would use TableSources for reading and > > TableSinks for writing ? > > And would that still work with our concept of Undo/Redo in OpenRefine to > > use Flink's Savepoints in concert with TableSources and TableSinks ? > That > > last part is where I am reading Flink docs now and still seeing a lot of > > fuzzyness, which worries me. > > > > -Thad > > +ThadGuidry <https://www.google.com/+ThadGuidry> > > > > > > > > > > > > > > -- > Thanks, > Andrew > > Subscribe to my book: Streaming Data <http://manning.com/psaltis> > <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306> > twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata> >
