Hi Jorge,
Are there places in the docs that you think this would simplify?
There is an old JIRA [1] about introducing a c-struct type that I
think aligns with this observation [1]
-Micah
[1] https://issues.apache.org/jira/browse/ARROW-1790
On Mon, Aug 30, 2021 at 2:57 PM Jorge Cardoso Leitão
wr
Congratulations Matt!
On Mon, Aug 30, 2021 at 5:36 PM Micah Kornfield wrote:
>
> On behalf of the Apache Arrow PMC, I'm happy to announce that Matt Topol
> has accepted an invitation to become a committer on Apache Arrow.
>
> Welcome and thank you for your contributions.
On behalf of the Apache Arrow PMC, I'm happy to announce that Matt Topol
has accepted an invitation to become a committer on Apache Arrow.
Welcome and thank you for your contributions.
My (incredibly naive) interpretation is that there are three problems to tackle.
1) How do you represent a graph and relational operators (join, union,
groupby, etc.)
- The PR appears to be addressing this question fairly well
2) How does a frontend query a backend to know what UDFs are supported
Hi,
Just came across this curiosity that IMO may help us to design physical
types in the future.
Not sure if this was mentioned before, but it seems to me that
`DaysMilliseconds` and `MonthDayNano` belong to a broader class of physical
types "typed tuples" in that they are constructed by defining
Hey everyone,
There's some interesting discussion around types and where their location
is in the current PR [1] (and in fact whether to store them at all).
It would be great to get some community feedback on this [2] part of the PR
in particular, because the choice of whether to store types at a
for the avoidance of doubt, +1 on the vote: release :)
On Sat, Aug 28, 2021 at 12:12 PM Jorge Cardoso Leitão <
jorgecarlei...@gmail.com> wrote:
> +1
>
> Thanks, Andrew!
>
> On Sat, Aug 28, 2021 at 12:10 PM Andrew Lamb wrote:
>
>> Update here: the issue is that we made a chance that is not compat
