First, the subject of this email is IPC, which is confusing. From the
discussion it sounds like we are primarily talking about FFI. It sounds
like the options here are:
1. Silently realign unless user opts out of realignment
The user will not get any runtime errors (easier to use) but a method
+1
happy to try it
El vie, 21 mar 2025 a las 7:42, Jacob Quinn ()
escribió:
> +1
>
> On Thu, Mar 20, 2025 at 10:50 PM Sutou Kouhei wrote:
>
> > Hi,
> >
> > I would like to propose enabling GitHub Discussions on:
> >
> > * apache/arrow
> > * apache/arrow-adbc
> > * apache/arrow-cookbook
> > * ap
Congrats Ian!
On Thu, Mar 20, 2025, 9:18 AM Wes McKinney wrote:
> Congrats!
>
> On Thu, Mar 20, 2025 at 7:37 AM Neal Richardson <
> neal.p.richard...@gmail.com>
> wrote:
>
> > Congratulations!
> >
> > On Thu, Mar 20, 2025 at 8:16 AM Rok Mihevc wrote:
> >
> > > Congrats Ian! Well deserved!
> > >
If that is the eventual outcome of this discussion, I would be happy to,
however, I'd like to avoid fragmenting the discussion just yet.
On 27/03/2025 17:18, Antoine Pitrou wrote:
Le 27/03/2025 à 18:14, Raphael Taylor-Davies a écrit :
It's obviously preferrable to be zero-copy but it's certai
I am using flight but in a fairly specific way, so my opinion may not be useful
for your case. But, I think you can use a variety of ways to handle a variety
of cases: - if your predicate is simple or compact you can specify to
Get/Exchange- if your predicate has a large representation or is com
Le 27/03/2025 à 18:14, Raphael Taylor-Davies a écrit :
It's obviously preferrable to be zero-copy but it's certainly not
mandatory, especially as the data being shared is assumed to be
read-only in most use cases.
In which case we should probably remove the comment about alignment from
the C i
It's obviously preferrable to be zero-copy but it's certainly not
mandatory, especially as the data being shared is assumed to be
read-only in most use cases.
In which case we should probably remove the comment about alignment from
the C interface specification, and highlight that implementatio
Hello,
Le 27/03/2025 à 17:53, Raphael Taylor-Davies a écrit :
The current ambiguity, however, makes it hard to set reasonable
defaults, as it isn't clear if FFI should be zero-copy and therefore
have alignment restrictions or not.
It's obviously preferrable to be zero-copy but it's certainl
Hi All,
Further context on Felipe's comment can be found [1]. You will note
arrow-rs can align on read, and in fact does do so by default in its IPC
reader, and by extension its flight client, the objection was solely to
always doing this over FFI, where it should at the very least be
configu
Hi,
All this complexity everywhere when arrow-rs could simply check the
alignment when they ingest external buffers and re-allocate to ensure
alignment.
I'm in favor of producers of Arrow arrays like a Flight client ensuring
alignment as early as possible (when buffers are allocated for arrays
de
This feels like it's trying to use Flight as a catalog service.
On Wed, Mar 26, 2025 at 6:04 PM Rusty Conover
wrote:
> Hi Jacob and Matt,
>
> I appreciate the opportunity to review the document. It helped clarify some
> things for me, but I’d like to propose an approach that is slightly
> differ
Indeed, it doesn't sound like a terrific use of Arrow maintainer time...
Especially as there's a growing feeling that Flight was not very well
designed, and should perhaps be slowly obsoleted in favor of more
focussed initiative (such as the Arrow-over-HTTP effort that's still not
finished :-
It's not clear to me why (4) doesn't work. Can you speak more about the flow of
requests here? Putting a ticket inside a FlightDescriptor makes me think
something more complicated is going on.
Alternatively...just create your own gRPC service, and return whatever payload
you need. There's no ne
Hi everyone,
I’d like to discuss the possibility of sending filtering predicates to an
Arrow Flight server. Currently, it’s unclear what the "proper" approach is
for achieving this.
The GetFlightInfo method only accepts a FlightDescriptor without additional
parameters. If it allowed for extra par
Congratulations Ian
El jue, 20 mar 2025, 9:28, Gang Wu escribió:
> Congrats Ian!
>
> On Thu, Mar 20, 2025 at 4:10 PM Ruoxi Sun wrote:
>
> > Congrats Ian!
> >
> > And my special appreciation for your consistently wonderful hosting of
> the
> > community meeting!
> >
> > *Regards,*
> > *Rossi SUN
Hi devs,
we are planning to add a new IPC read option:
|IpcReadOptions.ensure_memory_alignment|
This makes the IPC reader ensure that returned data are memory aligned
(as for instance required by Apache Arrow Rust).
Default is |false| as it is understood that data from gRPC always has to
be re
Hi,
This seems like a sensible approach and an improvement to developer/user
experience.
Rusty
Hi,
The vote carries with 5 +1 binding votes.
Let's discuss the new repository name as suggested by Bryce.
Should we use arrow-dotnet not arrow-csharp?
FYI: The number of GitHub repositories that include "dotnet" or
"csharp" in their name:
* "dotnet": 164K
https://github.com/search?q=dotnet&t
18 matches
Mail list logo
