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

Barrage Ingestion: Fix ClassCastExceptions on Empty Primitive Arrays #5503

Merged

Conversation

nbauernfeind
Copy link
Member

No description provided.

@nbauernfeind nbauernfeind enabled auto-merge (squash) May 16, 2024 22:49
@devinrsmith devinrsmith linked an issue May 16, 2024 that may be closed by this pull request
Copy link
Member

@devinrsmith devinrsmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've marked this as the proper fix for #5498; tested locally with my reproducer and all seemed good.

@nbauernfeind nbauernfeind merged commit 6351877 into deephaven:main May 16, 2024
14 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators May 16, 2024
devinrsmith added a commit that referenced this pull request May 17, 2024
This was originally explored as a fix for #5498; ultimately, it was an upstream data issue that was solved in #5503. Along the way though, it was noted that ring chunk sources were 1) using reflection in places they didn't need to, and 2) using specifically typed arrays for generic types as opposed to other object chunks which use `Object[]` at the top layer. In the latest iteration of this, the construction reflection was removed (there is a new getLength check); but I'm apt to keep the more specifically typed arrays unless we know they are causing other issues. At a minimum, the specifically typed arrays helped us notice and fix #5503.
stanbrub pushed a commit that referenced this pull request May 17, 2024
This was originally explored as a fix for #5498; ultimately, it was an upstream data issue that was solved in #5503. Along the way though, it was noted that ring chunk sources were 1) using reflection in places they didn't need to, and 2) using specifically typed arrays for generic types as opposed to other object chunks which use `Object[]` at the top layer. In the latest iteration of this, the construction reflection was removed (there is a new getLength check); but I'm apt to keep the more specifically typed arrays unless we know they are causing other issues. At a minimum, the specifically typed arrays helped us notice and fix #5503.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ring table nested array mis-match
3 participants