You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Marc Prud'hommeaux <mp...@apache.org> on 2021/02/08 15:41:42 UTC

[Rust] Datafusion table un-registration

I have a long-running ExecutionContext that needs to have parquet files registered and un-registered over time. Registration happens via register_table(), but there doesn't seem to be any corresponding unregister_table() function to later remove the table.

Is this something that might be useful to add? Would it just be a matter of removing the table from the datasources map?

Re: [Rust] Datafusion table un-registration

Posted by Marc Prud'hommeaux <mp...@apache.org>.
Andy–

Great! I've submitted a PR:

  https://github.com/apache/arrow/pull/9445

    –Marc

On 2021/02/08 15:53:37, Andy Grove <an...@gmail.com> wrote: 
> Hi Marc,
> 
> Yes, that sounds like a good addition, and yes, it should be as simple as
> removing it from the datasources map (although I haven't looked at that
> code lately).
> 
> Thanks,
> 
> Andy.
> 
> 
> On Mon, Feb 8, 2021 at 8:41 AM Marc Prud'hommeaux <mp...@apache.org>
> wrote:
> 
> > I have a long-running ExecutionContext that needs to have parquet files
> > registered and un-registered over time. Registration happens via
> > register_table(), but there doesn't seem to be any corresponding
> > unregister_table() function to later remove the table.
> >
> > Is this something that might be useful to add? Would it just be a matter
> > of removing the table from the datasources map?
> >
>

Re: [Rust] Datafusion table un-registration

Posted by Andy Grove <an...@gmail.com>.
Hi Marc,

Yes, that sounds like a good addition, and yes, it should be as simple as
removing it from the datasources map (although I haven't looked at that
code lately).

Thanks,

Andy.


On Mon, Feb 8, 2021 at 8:41 AM Marc Prud'hommeaux <mp...@apache.org>
wrote:

> I have a long-running ExecutionContext that needs to have parquet files
> registered and un-registered over time. Registration happens via
> register_table(), but there doesn't seem to be any corresponding
> unregister_table() function to later remove the table.
>
> Is this something that might be useful to add? Would it just be a matter
> of removing the table from the datasources map?
>