In the interest of avoiding bit-rot I'm OK with checking in the PR once its been reviewed, but we probably shouldn't do an official release of it (I'm not sure if this is feasible with our current release scripts).
On Sun, Aug 22, 2021 at 2:46 PM David Li <lidav...@apache.org> wrote: > Sorry, you're right - I got the process mixed up. Having two > implementations ready before a vote was discussed a few years back [1] so > we should have the C++ implementation ready first. Apologies for the > confusion. > > In the meantime, I'll give the Java implementation a more thorough review > when I get a chance. > > -David > > [1]: > https://lists.apache.org/thread.html/facecb2e6d9d7021bd613d7d979a00334b0a97121cb984fa832ec829%40%3Cdev.arrow.apache.org%3E > > On Sun, Aug 22, 2021, at 16:51, Micah Kornfield wrote: > > > > > > > To Micah's question, yes, we're going to hold a vote and treat it as > > > part of the spec, though even then like Flight itself it will be > > > "experimental" for a time. > > > > > > I'm not quite clear on what we would be voting on without the second > > implementation being present (even if it remains pre-1.0.0 after the > > initial version. I suspect we might want a different version number for > > Flight SQL?) > > > > -Micah > > > > On Thu, Aug 19, 2021 at 12:40 PM David Li <lidav...@apache.org> wrote: > > > > > To Micah's question, yes, we're going to hold a vote and treat it as > part > > > of the spec, though even then like Flight itself it will be > "experimental" > > > for a time. > > > > > > I think given the progress here, at least if there's no major comments > > > about the Protobuf spec itself, we should be holding a vote in the near > > > future. > > > > > > -David > > > > > > On Thu, Aug 19, 2021, at 13:40, Kyle Porter wrote: > > > > I believe that is the expectation, however not being fluent in the > full > > > > workings I defer to those who know better. > > > > > > > > I can say that the C++ implementation will be something we will be > > > working > > > > on in the immediate future. > > > > > > > > *Kyle Porter* > > > > CEO > > > > Bit Quill Technologies Inc. > > > > Office: +1.778.331.3355 | Direct: +1.604.441.7318 | > > > ky...@bitquilltech.com > > > > https://www.bitquill.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. > > > > > > > > > > > > On Thu, Aug 19, 2021 at 10:26 AM Micah Kornfield < > emkornfi...@gmail.com> > > > > wrote: > > > > > > > > > I just wanted to confirm that the intent is that this is going to > be > > > > > treated as an addition to the spec (so before adoption there will > be a > > > C++ > > > > > implementation and formal Vote). In the meantime it will be > treated as > > > > > experimental? > > > > > > > > > > -Micah > > > > > > > > > > On Thu, Aug 19, 2021 at 9:19 AM Kyle Porter < > ky...@bitquilltech.com > > > > > .invalid> > > > > > wrote: > > > > > > > > > > > Thanks Aldrin, > > > > > > > > > > > > Yes, Flight SQL should be language agnostic where the initial > > > > > > implementation is in Java. There are plans to create the C++ > > > > > implementation > > > > > > as well after, and then others can be worked on as needed. > > > > > > > > > > > > Best, > > > > > > > > > > > > *Kyle Porter* > > > > > > CEO > > > > > > Bit Quill Technologies Inc. > > > > > > Office: +1.778.331.3355 | Direct: +1.604.441.7318 | > > > > > ky...@bitquilltech.com > > > > > > https://www.bitquill.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. > > > > > > > > > > > > > > > > > > On Thu, Aug 19, 2021 at 9:15 AM Aldrin <akmon...@ucsc.edu.invalid > > > > > > > wrote: > > > > > > > > > > > > > Thanks Kyle! > > > > > > > > > > > > > > Out of curiosity, I don't see links to FlightSQL PRs/issues > for the > > > > > other > > > > > > > languages. I assume the proto itself would be language > agnostic, > > > and I > > > > > > > haven't followed closely enough to know the status of > > > implementations > > > > > for > > > > > > > the other languages. Is that something that is usually tracked > in > > > PRs > > > > > and > > > > > > > issues? > > > > > > > > > > > > > > I ask because the PR and linked JIRA issue have the [java] tag > so > > > I am > > > > > > not > > > > > > > sure how much of this PR is java specific. > > > > > > > > > > > > > > > > > > > > > On Wed, Aug 18, 2021 at 08:47 Kyle Porter < > ky...@bitquilltech.com > > > > > > .invalid> > > > > > > > wrote: > > > > > > > > > > > > > > > Hello All, > > > > > > > > > > > > > > > > We've been working on adding Flight SQL as a formal part of > Arrow > > > > > > Flight > > > > > > > > and the PR is available for review at > > > > > > > > https://github.com/apache/arrow/pull/10906. > > > > > > > > > > > > > > > > Most of the spec is now in place and, if you are interested, > it > > > would > > > > > > be > > > > > > > > good to have more eyes on the PR. > > > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > *Kyle Porter* > > > > > > > > CEO > > > > > > > > Bit Quill Technologies Inc. > > > > > > > > Office: +1.778.331.3355 | Direct: +1.604.441.7318 | > > > > > > > ky...@bitquilltech.com > > > > > > > > https://www.bitquill.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. > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Aldrin Montana > > > > > > > Computer Science PhD Student > > > > > > > UC Santa Cruz > > > > > > > > > > > > > > > > > > > > > > > > > > > >
