-
Notifications
You must be signed in to change notification settings - Fork 27
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
Improve Error Message When Data Type is Not Supported (Or Convert) #98
Comments
It might be nice to have some auto-conversions, though I'm not sure how I feel about how permissive it should be. My first instinct would be to allow only auto-conversions where Where this gets hairy is that, in your example, your We definitely should improve the error message. Of course this is not too difficult, but I have been considering doing a more comprehensive rewrite of some of the componenets that might make this even easier. The problem the package has right now is that the metadata writing process is weirdly separate from the process of actually writing the columns. This is due in large part to how the format works (the metadata is all stored in a separate flat buffer), but I feel it should be a bit more unified in the source code, see discussion in #86. |
hi EM. just wanted to suggest little improvements as I am playing around with it. feel free to close. best, /iaw |
At a minimum at some point we will improve the error messages, so I won't close this issue until that happens. |
Feather does not support storing |
Some conversions would definitely be nice (we already have |
I'm going to close this issue since it's specifically about an error message that has now been implemented. Feel free to open new issues about conversions. |
I just had a weird error
eventually, it dawned on me that my data frame had a char column, and that this was the problem.
so, I would suggest
I hope that both are easy fixes.
The text was updated successfully, but these errors were encountered: