I missed this call (incidentally to present Flight SQL at Subsurface). I'd be interested in helping to champion Flight SQL. What would this entail? Working on extending the documentation, providing example code and cookbook entries?
On Wed, Mar 2, 2022 at 10:59 AM Gavin Ray <ray.gavi...@gmail.com> wrote: > Ah got it, thank you! =) > > On Wed, Mar 2, 2022 at 10:33 AM Micah Kornfield <emkornfi...@gmail.com> > wrote: > > > Hi Gavin, > > This was mostly discussing the current discussion on the e-mail thread > > titled "Flight/FlightSQL Optimization for Small Results?". The main > thing > > discussed was whether we think adding the complexity around negotiation > is > > necessary. The consensus was it probably depends on how big the results > > will be. The other item discussed is whether the results should be > inlined > > on a ticket instead of FlightInfo. The main complexity there is how much > > custom parsing we want to do, which again depends on intended size of > > inlined data. > > > > -Micah > > > > On Wed, Mar 2, 2022 at 10:22 AM Gavin Ray <ray.gavi...@gmail.com> wrote: > > > >> Particularly curious about the small-results FlightSQL optimizations and > >> general FlightSQL developments, if there was anything anyone felt was > worth > >> noting outside of the general outline. > >> > >> Thank you =) > >> > >> On Wed, Mar 2, 2022 at 10:12 AM Micah Kornfield <emkornfi...@gmail.com> > >> wrote: > >> > >>> It was not. Is there anything you would like more context on? > >>> > >>> On Wed, Mar 2, 2022 at 10:10 AM Gavin Ray <ray.gavi...@gmail.com> > wrote: > >>> > >>> > Was this recorded by any chance? No worries if not. > >>> > > >>> > On Wed, Mar 2, 2022 at 9:58 AM Alessandro Molina < > >>> > alessan...@ursacomputing.com> wrote: > >>> > > >>> > > Attendees: > >>> > > > >>> > > > >>> > > Alessandro Molina > >>> > > > >>> > > Micah Kornfield > >>> > > > >>> > > David Li > >>> > > > >>> > > Joris Van Den Bossche > >>> > > > >>> > > > >>> > > > >>> > > Discussion: > >>> > > > >>> > > > >>> > > Flight SQL Optimization for Small Results > >>> > > > >>> > > - Reference to > >>> > > > >>> > > > >>> > > >>> > https://databricks.com/blog/2021/08/11/how-we-achieved-high-bandwidth-connectivity-with-bi-tools.html > >>> > > > >>> > > > >>> > > - Building directly in Flight as flight will benefit from it too. > >>> > > > >>> > > > >>> > > Binary VS String KeyValue Metadata > >>> > > > >>> > > - Resuscitate the discussion on ML -> [DISCUSS] Binary Values in > >>> Key > >>> > > value pairs > >>> > > > >>> > > - It is technically a breaking change and older clients expect > the > >>> > > previous format. > >>> > > > >>> > > > >>> > > GeoData JSON vs Binary > >>> > > > >>> > > - Binary doesn’t seem very hard in the majority of cases > >>> > > > >>> > > - base64 might add unnecessary overhead > >>> > > > >>> > > > >>> > > FlightSQL > >>> > > > >>> > > - Lack of documentation, not referenced from the website > >>> > > > >>> > > - Probably needing another community developer acting as champion > >>> for > >>> > the > >>> > > FlightSQL, David Li has been overseeing efforts, but the current > >>> > > contributions seem more focused on internal usage. > >>> > > > >>> > > On Wed, Mar 2, 2022 at 1:03 PM Ian Cook <i...@ursacomputing.com> > >>> wrote: > >>> > > > >>> > > > Hi all, > >>> > > > > >>> > > > Our biweekly sync call is today at 12:00 noon Eastern time. > >>> > > > > >>> > > > The Zoom meeting URL for this and other biweekly Arrow sync calls > >>> is: > >>> > > > > https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09 > >>> > > > > >>> > > > Alternatively, enter this information into the Zoom website or > app > >>> to > >>> > > > join the call: > >>> > > > Meeting ID: 876 4903 3008 > >>> > > > Passcode: 958092 > >>> > > > > >>> > > > Thanks, > >>> > > > Ian > >>> > > > > >>> > > > >>> > > >>> > >> > -- *James Duong* Lead Software Developer Bit Quill Technologies Inc. Direct: +1.604.562.6082 | jam...@bitquilltech.com https://www.bitquilltech.com This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.
