-
Notifications
You must be signed in to change notification settings - Fork 17
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
TypeError: can not serialize 'Series' object while trying to read remote intake_sql.intake_sql.SQLSource #13
Comments
I think, essentially, you will need to have arrow installed for both the server and client environments ( intake/intake#462 ). The branch that is getting activated should be giving you a meaningful error instead of the traceback you got. |
@danielballan , I know |
@emericauger , I will investigate further next week, and may move this issue to intake-sql. |
Even with arrow installed the traceback is the same. |
I transferred this issue to intake-sql. I also created #12 (and updated the CI with it, which is why I merged immediately). That PR shows a server-based workflow like yours, but it passes. I am not sure how you hit the error you came across. Perhaps you can recreate with a test function working with a sqlite file? |
I made two test functions : one with a sqlite file and an other with the Postgres database as a source. They both failed with the same issue. Test output
Full debug log on the server side
|
Sorry to ask more, but can you paste the sqlite test (no need for traceback), including code to generate the file and run the server. |
I finally found which causes the error : direct_access was not specified in catalog entries and default seems to be forbid. If that's helpful I made a test function to try an other sqlite file : add to utils.py :
with some modifications in test_sql_cat.py :
Thank you very much for your guidance ! |
I'm glad you solved it with direct access, but it is supposed to work via streaming too, so I'll get around to fixing the issue - and thanks, too, for providing the test case, it should be helpful. |
Using intake-sql.
It seems because msgpack recieve invalid data types in the response.
Traceback (server side) :
The text was updated successfully, but these errors were encountered: