There are 2 remaining problems in the write side API refactor <https://docs.google.com/document/d/1vI26UEuDpVuOjWw4WPoH2T6y8WAekwtI7qoowhOFnI4/edit?usp=sharing> : 1. how to put the `queryId` parameter in the write API 2. how to put the streaming OutputMode parameter in the write API
I'd like to discuss it and hopefully we can get a consensus to move forward. Thanks, Wenchen On Thu, Jan 10, 2019 at 2:40 AM Ryan Blue <rb...@netflix.com.invalid> wrote: > Hi everyone, > > This is a quick reminder that there is a DSv2 community sync tonight at 5 > PM PST. These community syncs are open to anyone that wants to participate. > If you’d like to be added to the invite, please send me a direct message. > > The main topic for this sync is the catalog API. To make discussion > easier, I think we should separate the current discussion into a few > orthogonal areas and discuss each: > > - Catalog API plugin system > - Plan for migration to a new catalog API > - Catalog API design approach using separate interfaces (TableCatalog, > UDFCatalog, FunctionCatalog, etc.) > - TableCatalog API proposal > > <https://docs.google.com/document/d/1zLFiA1VuaWeVxeTDXNg8bL6GP3BVoOZBkewFtEnjEoo/edit#heading=h.lljaf71h0p55> > and > implementation, PR #21306 <https://github.com/apache/spark/pull/21306> > (not the proposed user-facing API) > > If we have time, we can also talk about the user-facing API > <https://docs.google.com/document/d/1zLFiA1VuaWeVxeTDXNg8bL6GP3BVoOZBkewFtEnjEoo/edit#heading=h.cgnrs9vys06x> > proposed in the SPIP. > > Thanks, > > rb > -- > Ryan Blue > Software Engineer > Netflix >
