You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like a way to append just a single new TableFactory to the list of factories being constructed
Also it should have
Documentation
Tests (ideally a doc test with an example of how to use to use it)
Describe alternatives you've considered
I recommend adding a new function SessionStateBuilder::with_table_factory that works like this:
let state = SessionStateBuilder::new().with_table_factory("DELTA", factory1).wth_table_facotry("ICEBERG", facotry2)// resulting state has both factory1 and factory2.build()
Additional context
No response
The text was updated successfully, but these errors were encountered:
alamb
changed the title
Improve SessionStateBuilder to add a single new table_factory
Support adding a single new table factory to SessionStateBuilderSep 20, 2024
Is your feature request related to a problem or challenge?
Part of #12550
While working on https://github.com/datafusion-contrib/datafusion-dft I want to register various types of extensions while configuring the SessionContext, ideally adding each extension to the
SessionStateBuilder
each time.However, I found that there were a few APIs missing on SessionStateBuilder so I had to implement my own workaround builder here: https://github.com/datafusion-contrib/datafusion-dft/blob/8247555f9464058c1ac3370196739ac2b19343ee/src/extensions/builder.rs#L84-L98
SessionStateBuilder
hasSessionStateBuilder::with_table_factories
method to set all the table factories, but no way to just append a new table factoryDescribe the solution you'd like
I would like a way to append just a single new
TableFactory
to the list of factories being constructedAlso it should have
Describe alternatives you've considered
I recommend adding a new function
SessionStateBuilder::with_table_factory
that works like this:Additional context
No response
The text was updated successfully, but these errors were encountered: