+1
On Thu, Aug 19, 2021 at 9:18 AM Wes McKinney wrote:
>
> +1
>
> On Thu, Aug 19, 2021 at 6:20 PM Antoine Pitrou wrote:
> >
> >
> > Hello,
> >
> > I would like to propose clarifying the allowed value range for the Time
> > types. Specifically, I would propose that:
> >
> > 1) allowed values fal
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
+1
On Thu, Aug 19, 2021 at 6:20 PM Antoine Pitrou wrote:
>
>
> Hello,
>
> I would like to propose clarifying the allowed value range for the Time
> types. Specifically, I would propose that:
>
> 1) allowed values fall between 0 (included) and 86400 seconds
> (excluded), adjusted for the time uni
I wanted to draw attention to a PR[1] in the DataFusion repository that
proposes a API designed to abstract away access to remote datasources, to
allow plugging in sources such as S3.
It has had some great discussion and community engagement so far but given
it is a fairly significant change to
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 (binding)
Thank you
On Thu, Aug 19, 2021 at 11:12 AM Rok Mihevc wrote:
> +1 (non-binding)
>
> On Thu, Aug 19, 2021 at 2:12 PM Joris Van den Bossche
> wrote:
> >
> > +1
> >
> > On Wed, 18 Aug 2021 at 20:16, David Li wrote:
> >
> > > +1
> > >
> > > On Wed, Aug 18, 2021, at 10:31, Neal Richar
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
wrote:
> Than
Hello,
I would like to propose clarifying the allowed value range for the Time
types. Specifically, I would propose that:
1) allowed values fall between 0 (included) and 86400 seconds
(excluded), adjusted for the time unit;
2) leap seconds cannot be represented (see above: 86400 is outsi
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
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
+1 (non-binding)
On Thu, Aug 19, 2021 at 2:12 PM Joris Van den Bossche
wrote:
>
> +1
>
> On Wed, 18 Aug 2021 at 20:16, David Li wrote:
>
> > +1
> >
> > On Wed, Aug 18, 2021, at 10:31, Neal Richardson wrote:
> > > +1
> > >
> > > On Wed, Aug 18, 2021 at 6:06 AM Antoine Pitrou
> > wrote:
> > >
> >
+1
On Wed, 18 Aug 2021 at 20:16, David Li wrote:
> +1
>
> On Wed, Aug 18, 2021, at 10:31, Neal Richardson wrote:
> > +1
> >
> > On Wed, Aug 18, 2021 at 6:06 AM Antoine Pitrou
> wrote:
> >
> > > +1 (binding)
> > >
> > >
> > > Le 17/08/2021 à 21:49, Micah Kornfield a écrit :
> > > > Hello,
> > >
Just a note - you are most welcome to contribute to Airlfow as well :D
J.
On Thu, Aug 19, 2021 at 8:04 AM Calvin Chiang
wrote:
> Hi Neal
>
> Ooops thanks! yes i meant Arrow :)
> Great thanks for the link to the dev environment setup - not sure how i
> missed that one.
> i'll check out some jir
13 matches
Mail list logo
