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

[bugfix]Fix a mismatch between the type of jdbc query result and the datatype #512

Closed
wants to merge 5 commits into from

Conversation

Zhumengze
Copy link
Contributor

Proposed changes

Issue Number: close #xxx

Problem Summary:

The value type obtained by rs.getObject(index + 1) is inconsistent with the field type obtained by flink Context, resulting in a conversion failure in encapsulating flink RowData. For example, the java type corresponding to TINYINT is Java.lang. Byte, while the java type obtained by rs.getObject(index + 1) is Java.lang. Integer, which has a type conversion problem. SMALLINT had the same problem.

Checklist(Required)

  1. Does it affect the original behavior: (Yes/No/I Don't know)
    NO
  2. Has unit tests been added: (Yes/No/No Need)
    YES
  3. Has document been added or modified: (Yes/No/No Need)
    NO
  4. Does it need to update dependencies: (Yes/No)
    NO
  5. Are there any changes that cannot be rolled back: (Yes/No)
    NO

Further comments

If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...

"bigintColumn" +
" from `datagen`" +
" inner join `doris_lookup` FOR SYSTEM_TIME AS OF datagen.proctime on datagen.id = doris_lookup.id").print();
env.execute("Flink doris lookup test");
Copy link
Member

@JNSimba JNSimba Nov 18, 2024

Choose a reason for hiding this comment

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

How do we judge whether this result is in line with expectations?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You can run the test case in the previous code and the bug will show up

Copy link
Member

Choose a reason for hiding this comment

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

This test appears to run continuously and not complete automatically?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes,this is a streaming job.

Copy link
Member

Choose a reason for hiding this comment

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

This may be a problem because it will cause the test case to fail to complete.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, I'll change it later

@JNSimba
Copy link
Member

JNSimba commented Nov 18, 2024

Thanks for your contribution, some CI failed, @Zhumengze PTAL

@Zhumengze
Copy link
Contributor Author

@JNSimba
The above issues have been fixed, and a new PR has been submitted, please see more information #514

@Zhumengze Zhumengze closed this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants