-
Notifications
You must be signed in to change notification settings - Fork 104
fix(file-service): avoid manually constructing the Dataset object through parameters #3820
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
Conversation
|
Our common practice is to create an issue and use a PR to fix the issue. So please create an issue. It's also a good chance to check the PR #3812 and follow the new bug-report template to create the issue. |
Added. Please check |
|
Thanks. Do you think a test case can be added? |
|
This is the correct approach. We should apply the same fix to all other instances, if any. |
Added. Please check |
28561ab to
fd311a3
Compare
|
@aicam Please review it first. |
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.
LGTM! in general we are using so many different formats of database querying, we may make them consistent in the future, @chenlica should I add an issue for it?
Use createdDataset.into(classOf[Dataset]) to convert DatasetRecord to Dataset POJO instead of manually constructing with parameters to avoid non-deterministic parameter ordering issues. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
738d8eb to
d494008
Compare
Summary
createdDataset.into(classOf[Dataset])to convert DatasetRecord to Dataset POJO instead of manual constructorFixes #3821