[ 
https://issues.apache.org/jira/browse/BEAM-7210?focusedWorklogId=239221&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-239221
 ]

ASF GitHub Bot logged work on BEAM-7210:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/May/19 14:18
            Start Date: 08/May/19 14:18
    Worklog Time Spent: 10m 
      Work Description: reuvenlax commented on issue #8474: [BEAM-7210] Fix 
non-deterministic row access
URL: https://github.com/apache/beam/pull/8474#issuecomment-490504391
 
 
   Yes. I think most users will access the Row by name though, not by index.
   If users have an object (POJO, Avro, AutoValue, etc.) with a matching
   schema, they can instead just access via that object and not bother with
   the Row object at all.
   
   On Wed, May 8, 2019 at 3:37 AM Maximilian Michels <[email protected]>
   wrote:
   
   > I see. So on Rows users need to ensure that they either know the structure
   > of the Row or go through the Schema which returns the correct index for a
   > field name. Thanks!
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/beam/pull/8474#issuecomment-490436886>, or mute
   > the thread
   > 
<https://github.com/notifications/unsubscribe-auth/AFAYJVKQ6HT7ZS4ZRDIJY2DPUKUM7ANCNFSM4HKCZFNQ>
   > .
   >
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 239221)
    Time Spent: 1h 20m  (was: 1h 10m)

> Test ParDoSchemaTest#testInferredSchemaPipeline is flaky
> --------------------------------------------------------
>
>                 Key: BEAM-7210
>                 URL: https://issues.apache.org/jira/browse/BEAM-7210
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink, sdk-java-core
>            Reporter: Maximilian Michels
>            Assignee: Reuven Lax
>            Priority: Major
>             Fix For: 2.13.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Test ParDoSchemaTest#testInferredSchemaPipeline is flaky. Please see 
> [https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink/3918/testReport/junit/org.apache.beam.sdk.transforms/ParDoSchemaTest/testInferredSchemaPipeline/]
> It seems like the backing row data is not populated in a deterministic way:
> {noformat}
> Caused by: java.lang.ClassCastException: java.lang.Integer cannot be cast to 
> java.lang.String
>       at org.apache.beam.sdk.values.Row.getString(Row.java:279)
>       at 
> org.apache.beam.sdk.transforms.ParDoSchemaTest$12.process(ParDoSchemaTest.java:391){noformat}
> CC [~reuvenlax]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to