Omega359 commented on issue #13625:
URL: https://github.com/apache/datafusion/issues/13625#issuecomment-2517794438
> @alamb yep that fixes it
>
> ```
> let config = SessionConfig::new()
>
.set_bool("datafusion.execution.parquet.schema_force_view_types", false);
>
> // Create a SessionState using the config and runtime_env
> let state = SessionStateBuilder::new()
> .with_config(config)
> .with_default_features()
> .build();
>
> // Create a SessionContext
> let ctx = SessionContext::from(state);
> ```
My guess is that you are being impacted by the issue being worked on in
https://github.com/apache/datafusion/pull/13404
> I think one small frustration I've had with datafusion is the amount of
backwards breaking changes. Is it fair to say that datafusion isn't ready for
production yet? Are there any active plans to add a more comprehensive test
suite so users can feel confident more confident with the updates? Or perhaps
are there any config settings that I can opt into that trades off stability for
performance?
As far as tests there is this:
https://github.com/apache/datafusion/issues/13470 however I don't believe that
will cover a large portion of what is breaking between releases for people, at
least not initially.
As far as being production ready I suppose that depends on your definition
of production ready. It's being used in production by quite a few companies for
some time now but upgrades do seem to have been a concern -
https://github.com/apache/datafusion/issues/13525
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
