[
https://issues.apache.org/jira/browse/BEAM-4706?focusedWorklogId=123011&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-123011
]
ASF GitHub Bot logged work on BEAM-4706:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Jul/18 19:35
Start Date: 13/Jul/18 19:35
Worklog Time Spent: 10m
Work Description: ElliottBrossard opened a new pull request #5948:
[BEAM-4706] Fix the expected encoding of BigQuery's NUMERIC type when reading
from Avro
URL: https://github.com/apache/beam/pull/5948
The NUMERIC data type is represented in Avro using the BYTES type with the
DECIMAL logical type.
I verified this change using BigQueryTornadoes.java, which I modified
(locally) to write NUMERIC values to BigQuery, then read them back using
Dataflow and write them to a new BigQuery table. The test failed as expected
without this change, but now passes, and I can see the correct content in the
table.
Context: https://github.com/apache/beam/pull/5755#issuecomment-402241675
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 123011)
Time Spent: 2h (was: 1h 50m)
> BigQueryTornadoesIT cannot be run using integrationTest and performanceTest
> tasks
> ---------------------------------------------------------------------------------
>
> Key: BEAM-4706
> URL: https://issues.apache.org/jira/browse/BEAM-4706
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Lukasz Gajowy
> Assignee: Kasia Kucharczyk
> Priority: Major
> Fix For: 2.6.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> It seems that we cannot run this test using tasks from BuildModulePlugin
> designed to run such tests. Those are not included in build.gradle of
> examples module. There's a possibility that some other tests are not able to
> run due to this reason (this also has to be checked).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
