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
Is your feature request related to a problem or challenge?
As we increase the number of functions in our core, it might lead to an increased runtime footprint for datafusion-cli in the future. This increase will be due to functions that a lot of users with specific use-cases in mind wouldn't need. The same can be claimed for users using the cli for a more general purpose.
Describe the solution you'd like
Adding a new feature wherein a user pass a flag while starting the datafusion-cli that will start the CLI with a "bare-bones" set of functions. These functions shall be the absolutely necessary ones. Then the user shall manually import the set of functions as needed.
This feature primarily aims to provide users with more customization along with a reduced runtime footprint.
Describe alternatives you've considered
No response
Additional context
This idea originated from the discussion on creating a separate crate for spark functions. The idea of having an import command was first mentioned there. This issue proposes to provide the import command in context of a custom cli.
Is your feature request related to a problem or challenge?
As we increase the number of functions in our core, it might lead to an increased runtime footprint for datafusion-cli in the future. This increase will be due to functions that a lot of users with specific use-cases in mind wouldn't need. The same can be claimed for users using the cli for a more general purpose.
Describe the solution you'd like
Adding a new feature wherein a user pass a flag while starting the
datafusion-cli
that will start the CLI with a "bare-bones" set of functions. These functions shall be the absolutely necessary ones. Then the user shall manually import the set of functions as needed.This feature primarily aims to provide users with more customization along with a reduced runtime footprint.
Describe alternatives you've considered
No response
Additional context
This idea originated from the discussion on creating a separate crate for spark functions. The idea of having an import command was first mentioned there. This issue proposes to provide the import command in context of a custom cli.
The original comment: #5600 (comment)
The text was updated successfully, but these errors were encountered: