I was thinking selection vector/bitmap (possibly with different encodings), but really nothing for now. Ordinarily, I'd lean towards YAGNI but there isn't a good way to add this in easily in a forward compatible way unless we add a placeholder enum/table for 1.0 (the default option would be no filter and wouldn't change the packaged data at all).
On Fri, Jan 24, 2020 at 4:55 AM Francois Saint-Jacques < fsaintjacq...@gmail.com> wrote: > By filter, you mean a filter expression, or a selection vector/bitmap? > > On Thu, Jan 23, 2020 at 11:38 PM Micah Kornfield <emkornfi...@gmail.com> > wrote: > > > > One of the things that I think got overlooked in the conversation on > having > > a slice offset in the C API was a suggestion from Jacques of perhaps > > generalizing the concept to an arbitrary "filter" for arrays/record > batches. > > > > I believe this point was also discussed in the past as well. I'm not > > advocating for adding it now but I'm curious if people feel we should add > > something to Schema.fbs for forward compatibility, in case we wish to > > support this use-case in the future. > > > > Thanks, > > Micah >
