Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Towards Extractor output format #4

Open
PeterKraus opened this issue Sep 11, 2024 · 1 comment
Open

Towards Extractor output format #4

PeterKraus opened this issue Sep 11, 2024 · 1 comment

Comments

@PeterKraus
Copy link
Contributor

PeterKraus commented Sep 11, 2024

We should think about how extractors can report their desired formats at 
some point (thinking e.g. if we'll have issues with pandas 3 etc)

Originally posted by @ml-evs in datatractor/beam#3 (review)

@PeterKraus
Copy link
Contributor Author

What we have now:

  • Support for specifying {{ output_type }} in templating, but requires the extractor to support it too,
  • Support for specifying supported_output_filetypes for an Extractor, at the moment it's "global" (i.e. not per-usage), but it could be adapted to match supported_filetypes

Of course, this deals with FileTypes only and not any returned in-memory objects. For usage.method == python, it might be sensible to also provide something like required_formats that indicates what package(s) (e.g. pandas, numpy < 2.0 etc.) needs to be installed in the parent env to be able to handle the returned object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant