-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Bug]: Encoding issue when reading BQ query result set in DataflowRunner #24870
Comments
CC: @ahmedabu98 who is investigating this issue |
The logical type causing problem is indeed
What confuses me is here: beam/sdks/java/core/src/main/java/org/apache/beam/sdk/schemas/SchemaCoderHelpers.java Lines 85 to 89 in 37c7bee
value is a java.time.LocalDate, then Date.toBaseType(value) should return a Long to baseType. However |
Logical type send to SchemaCoderHelpers is an "UnknownLogicalType" this is the problem. It has the |
I'm confused about why it was unknown when it is known in 2.42.0, and why this happened in 2.43.0 only for DataflowRunner but not DirectRunner. I also don't feel marking the logical type as unknown is a good idea either because the issue gets pushed downstream.
On Thursday, January 5, 2023 at 05:32:32 p.m. EST, Yi Hu ***@***.***> wrote:
Logical type send to SchemaCoderHelpers is an "UnknownLogicalType" this is the problem. It has the beam:logical_type:date:v1 though.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I think the issue is introduced in #23014. Will put a fix in. |
This issue likely affect all pipelines that involves portable but not standard logical types in schematranslation, set a milestone. Would provide a quick fix |
What happened?
I tried to run a pipeline that ran a SQL query with a BQ DATE field in the result set with DataflowRunner and it resulted in an encoding error. The exception message suggests that the correct coder was chosen (The Date logical type resolves to a Long) but the value resolution doesn't appear to happen with DataflowRunner. It did with DirectRunner.
FWIW I see another issue with a similar exception message. Any relation? #20906
Affected Runners: DataflowRunner (DirectRunner with 2.43.0 and previous versions was fine)
Affected Versions: 2.43.0 (2.41.0, 2.42.0 do not appear to exhibit this behaviour.)
Sample Code
Exception
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: