-
Notifications
You must be signed in to change notification settings - Fork 244
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
[query] Remove jackson string length restriction in Spark/Local backends #14651
[query] Remove jackson string length restriction in Spark/Local backends #14651
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you comment about how you've tested this? I think it might also be worth commenting in the source code why/in what circumstances strings might get so long?
As an aside, do you know why strings are getting so crazy long? Is that legit?
9e89f35
to
fd10c0b
Compare
@ehigham Think I've addressed everything. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the comments - that'll be helpful when reviewing this code in the future no doubt!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit concerned about the replication, and in the future making a change and forgetting to apply it in all three places. Instead of doing this in the apply
methods for each backend (and main
for the service backend), could we move it to the constructor of the Backend
superclass?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks Chris!
As mentioned in #14580, IR can get quite big, especially as it can contain an arbitrary amount of encoded literals from the user's python session.
Tested manually, by making a very very large literal, running a pipeline with it on 0.2.132, observing the failure seen in #14650, then running the same pipeline with this change, and it succeeds as normal.
Resolves #14650